fix(linter): error on dependencies that are only in devDependencies instead of production dependencies #18780
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it so that packages listed under
devDependencies
are not counted as correct. User must add the dependency todependencies
,peerDependencies
, oroptionalDependencies
sincedevDependencies
are not installed for the end user (consumer of the published project).For example, say I have a project with this
package.json
:And in my project I have
import 'foo'
somewhere in the source code.In the existing version of the dep checks rule, it will not error out. However, if a consumer installed my published package, they will get an error because
foo
package is not installed. The fix in this PR will force the user to movefoo
todependencies
,peerDependencies
, oroptionalDependencies
.Current Behavior
Adding a dependency to
devDependencies
satisfies the dep check.Expected Behavior
Dependency cannot only be in
devDependencies
.Related Issue(s)
Fixes #