Skip to content
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

Doesn't seem to support yarn v2 #1642

Closed
fifn2 opened this issue Feb 2, 2020 · 5 comments
Closed

Doesn't seem to support yarn v2 #1642

fifn2 opened this issue Feb 2, 2020 · 5 comments

Comments

@fifn2
Copy link

fifn2 commented Feb 2, 2020

Yarn v2 recently came out with a new module directory structure that doesn't seem to be supported by eslint-plugin-import.

@ljharb
Copy link
Member

ljharb commented Feb 2, 2020

I’m quite aware of it; see #1591, a PR from the yarn maintainer to make it compatible.

Are you on the latest version of the plugin?

@AlexandreBonaventure
Copy link

I'm running latest version of the plugin (2.20.1) and with yarn v2 I run into :
Resolve error: unable to load resolver "node" erros

@ljharb
Copy link
Member

ljharb commented Feb 5, 2020

I believe you'll need to add eslint-plugin-resolver-node to your top-level dev deps; either way, I think issues with yarn need to be filed on yarn.

@ljharb ljharb closed this as completed Feb 5, 2020
@constgen
Copy link

constgen commented Oct 7, 2020

https://github.com/benmosher/eslint-plugin-import/pull/1591/files
Looking to changes in this PR seems like it fixes only cases when eslint-plugin-import is installed directly in the project. But if the project imports another config which includes eslint-plugin-import then it doesn't work with Yarn 2.

So speaking simply the bug still persists. You just have to use dependency structure root-project-taht-is-linted -> my-custom-eslint-config -> eslint-plugin-import to reproduce it

Reopen?

@ljharb
Copy link
Member

ljharb commented Oct 7, 2020

@constgen anything that works in npm but breaks in yarn 2 is a bug in yarn 2; please feel free to file it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants