-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] eslint not working with eslint-plugin-import in an monorepo #1057
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I have the same problem with babel plugins that cannot be found, it is because some packages from workspace have several virtuals in I manage to temporarily fix the problem by manually modifying Note: If I remove the |
@arcanis I have not found a way to force the resolution of my packages to use the workspace directly, without going through virtuals, do you have a solution or a plan for that? |
pnpMode: "loose"
pnpFallbackMode: "all" This help me, waiting for eslint/rfcs#47 and eslint/eslint#12922 |
We can't do that as it would prevent access to peer dependencies, |
This comment has been minimized.
This comment has been minimized.
This issue reproduces on master:
|
This seems to have been fixed in #695 |
Describe the bug
When using
eslint
&eslint-plugin-import
in an monorepo, where we have dependencies on each other workspace - eslint is accessing the symlinked (from the workspace) folder and checking the eslint errors from that file. which results in following error:next i tried to re-produce this issue on an minimalistic setup - where everything worked fine. i even made the sherlock script to re-produce the error, but its not an issue on those setups. so i investigated and looked into differences in both.
as i looked into the
.pnp.js
of both - i saw that the common package gets linked a bit differently:and in the original error its even mentioning the virtual package
/Users/sschaffernak/dev/_yarnv2/application-engine/.yarn/$$virtual/@company-application-engine-common-virtual-f54925b670
so i think it has something to do with it.can somebody explain why there are two versions created by yarn in my pnp file?
Environment if relevant (please complete the following information):
The text was updated successfully, but these errors were encountered: