Versions
Repro steps
From an Angular 5 project:
- update the CLI to v6 and migrate
ng update @angular/core --next
Observed behavior
Pinned versions in package.json:
"@angular/compiler": "6.0.0-rc.5",
"@angular/core": "6.0.0-rc.5",
"typescript": "2.7.2"
...
Desired behavior
Keep semantic versionning in package.json:
"@angular/compiler": "^6.0.0-rc.5",
"@angular/core": "^6.0.0-rc.5",
"typescript": "~2.7.2"
...
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.
Versions
Repro steps
From an Angular 5 project:
ng update @angular/core --nextObserved 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 updateand 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.