ESLint 6.6.0 does not account for module-hoisting via yarn workspaces when determining path for plugins
See original GitHub issueTell us about your environment
Node version: v12.10.0 npm version: v6.2.0 Local ESLint version: Not found – But it is installed (rolled back to 6.5.1 and it’s working fine) Global ESLint version: v6.5.1 (Currently used)
What did you expect to happen? Upgrading from 6.5.1 to should not break linting (specifically seeing this in Sublime Text)
I get an error for the first plugin, no matter what plugin that is. The message I get is like this:
Error: Failed to load plugin 'react' declared in '.eslintrc': ENOENT: no such file or directory, open 'C:\projects\myProject\node_modules\eslint-plugin-react\node_modules\doctrine\lib\doctrine.js'
But we’re using yarn workspaces
and lerna
and the proper location of that file in our environment after upgrading to 6.6.0
is: C:\projects\myProject\node_modules\doctrine\lib\doctrine.js
What actually happened? Please include the actual, raw output from ESLint.
See error text above.
Are you willing to submit a pull request to fix this bug? Can’t help with resolution.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (5 by maintainers)
Top GitHub Comments
I have this same issue after upgrading, but I’m not using Sublime. I don’t think this is an issue with an external plugin. I’m having it while using yarn workspaces and Atom.
With all the moving parts here, it’s a bit of a wild goose chase at the moment. Sounds like it might be beneficial to file an issue with the Sublime plugin you’re using - they might be able to chase this down!