-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
eslint in dependencies rather than dev-dependencies after eject #3209
Comments
See #2696 for context -- basically there's no correct answer to the argument. |
No, |
@Timer there's definitely a correct answer, and the technicality of bundling doesn't alter it. Things that are used at runtime - even if via a bundling process - are dependencies, and things that are used to develop the package/app/module, are devDependencies. Every eslint thing should always be a devDependency; there's literally no reason beyond pedantry to argue otherwise. |
Why are these eslint packages in dependencies instead of dev-dependencies after eject? Wouldn't that make the production build size unnecessarily bigger?
The text was updated successfully, but these errors were encountered: