Skip to content
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

Yarn 1.5.1: upgrade doesn't properly update package.json for devDependencies #5602

Closed
josefglatz opened this issue Mar 30, 2018 · 1 comment
Assignees
Labels

Comments

@josefglatz
Copy link

Same behaviour as #1458: #1458 (comment)

@ghost ghost assigned rally25rs Mar 30, 2018
@ghost ghost added the triaged label Mar 30, 2018
@rally25rs
Copy link
Contributor

duplicate #4840

also note that as stated in the docs package.json does not change on an upgrade because it has no need to because it respects your specified semver range. yarn.lock will change to reflect the version upgraded to. An upgrade --latest may change your package.json if it needs to (unless the currently installed version is already the latest and matches the already specified range).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants