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

why using peerDependencies instead of DevDependencies? #1

Closed
LastStranger opened this issue Apr 30, 2022 · 1 comment
Closed

why using peerDependencies instead of DevDependencies? #1

LastStranger opened this issue Apr 30, 2022 · 1 comment

Comments

@LastStranger
Copy link

I know NPM7.X will auto-install peerDependdencies, but for NPM7.X early version users, they have to install those by themselves, which is not convenient, and I use Pnpm has the same issue, what's the good of using peerDependencies?

@mryechkin
Copy link
Owner

Because there is no executable code in shared configs (it's essentially just exporting a plain object), so it wouldn't make sense to package a bunch of dependencies with it. Users are expected to have ESLint and the other plugins installed in the consuming project, which is exactly what the peerDependencies field is for.

See these issues for more details:

eslint/eslint#3458

eslint/eslint#2518

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

No branches or pull requests

2 participants