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
Add an eslint rule to forbid adding devDependencies
in packages
#32390
Comments
I'll give this a shot. Looks like the no-extraneous-dependencies rule is actually a decent model for what we need. |
This issue has been marked as stale and will be closed in seven days. This happened because:
You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation. |
I think we're still working on this. Should be made easier / proper by #38190 |
Big part of this issue was solved in #36534 by @simison himself when he added the I pushed a commit to #38190 (its sha is ae80bab as I write this, but will change after the next rebase) that modifies the linter config to allow dev dependencies only in the root |
The original issue was raised when we were using I do think having packages with I'm closing this for now, if anybody has strong opinions about it we can revisit. |
If adding
devDependencies
topackage.json
in packages/apps can cause trouble (see e.g. #32383), we'll need an Eslint rule to stop folks doing this.Monorepo docs say:
Note also conflicting
import/no-extraneous-dependencies
rule in packages (#32294 (comment))FYI @Automattic/team-calypso
The text was updated successfully, but these errors were encountered: