You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
The existence of preferDev in a module's package.json will raise warnings when the module is being installed as a dependency instead of a devDependency.
What problem is the feature intended to solve?
This will help prevent adding packages like eslint, mocha, etc to dependencies accidentally.
Is the absence of this feature blocking you or your team? If so, how?
No, this feature is meant to be a usability improvement.
Is this feature similar to an existing feature in another tool?
Not that I know of.
Is this a feature you're prepared to implement, with support from the npm CLI team?
Yes
The text was updated successfully, but these errors were encountered:
I'm opening this issue because:
What's the feature?
The existence of
preferDev
in a module's package.json will raise warnings when the module is being installed as adependency
instead of adevDependency
.What problem is the feature intended to solve?
This will help prevent adding packages like
eslint
,mocha
, etc to dependencies accidentally.Is the absence of this feature blocking you or your team? If so, how?
No, this feature is meant to be a usability improvement.
Is this feature similar to an existing feature in another tool?
Not that I know of.
Is this a feature you're prepared to implement, with support from the npm CLI team?
Yes
The text was updated successfully, but these errors were encountered: