Skip to content

Dependency issues #157

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

Open
ekashida opened this issue Apr 17, 2025 · 2 comments
Open

Dependency issues #157

ekashida opened this issue Apr 17, 2025 · 2 comments

Comments

@ekashida
Copy link
Member

With the changes in #151, some peer dependencies have become actual dependencies:

These, and any others that may have been missed, should be moved to dependencies.

@ekashida
Copy link
Member Author

Not 100% sure this is an issue, it just seems strange to have to install all of these packages even when you're not using the specific config with the dependency. yarn why doesn't seem to report peer dep relationships either so you couldn't use that to remember why one of these was installed once you installed it, but I guess that issue always existed with plugins and peer deps.

@wjhsf
Copy link
Contributor

wjhsf commented Apr 17, 2025

It's standard practice for eslint configs to specify their plugins as peer deps. 🤷

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