[BUG] installing a dependency in a package with a peer dependency changes the peerDependencies field #3096
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Current Behavior:
If you have a package with
something
inpeerDependencies
and then install that something in the same package as a devDependency, the peerDependencies field is changed and the dependency is added topackage.json
, but it inherits the semver string that the peer dependency had.Expected Behavior:
Installing a dev dependency should do the same change to the
package.json
, whether that dependency is already inpeerDependencies
or not.Steps To Reproduce:
Environment:
The text was updated successfully, but these errors were encountered: