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
Mention any other details that might be useful (optional)
Pinned versions mean we can't do anymore minor/patch updates of the whole project simply with npm update and goes against semver.
It's not the role of the CLI to pin the versions. It's the role of the package manager, and as Angular 6 and CLI 6 require Node >= 8.9 and npm >= 5.5, it means the job is already done in a proper way by the package-lock.json.
The text was updated successfully, but these errors were encountered:
I'm pretty sure this is a dupe as we've talked about it internally, but can't find the original issue so marking this as required.
hansl
added
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
P5
The team acknowledges the request but does not plan to address it, it remains open for discussion
and removed
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
labels
Apr 23, 2018
Versions
Repro steps
From an Angular 5 project:
ng update @angular/core --next
Observed behavior
Pinned versions in
package.json
:Desired behavior
Keep semantic versionning in
package.json
:Mention any other details that might be useful (optional)
Pinned versions mean we can't do anymore minor/patch updates of the whole project simply with
npm update
and goes against semver.It's not the role of the CLI to pin the versions. It's the role of the package manager, and as Angular 6 and CLI 6 require Node >= 8.9 and npm >= 5.5, it means the job is already done in a proper way by the
package-lock.json
.The text was updated successfully, but these errors were encountered: