5 ms·
I created a new project using @angular/cli 1.6 which the release says is tied to Angular 5.1: https://github.com/angular/angular-cli/releases/tag/v1.6.0 https:/
by mythz 9y ago
I created a new project using @angular/cli 1.6 which the release says is tied to Angular 5.1: https://github.com/angular/angular-cli/releases/tag/v1.6.0 https://github.com/angular/angular-cli/releases/tag/v1.6.0
But all npm package.json dependencies are still anchored on the same ^5.0.0 dependencies that ng v1.5.0 had and still depends on typescript "~2.4.2", basically ignoring the 5.1 announcement.
How can we create a new Angular 5.1 App using ng? Are we meant to manually change all dependencies to ^5.1.0
- shusson 9y agoSee https://github.com/angular/angular-cli/pull/8766 https://github.com/angular/angular-cli/pull/8766
- mythz 9y agoI manually updated the typescript dependency which breaks the build, even when manually upgrading the compiler-cli to ^5.1.0, so basically 5.1 doesn't work with typescript 2.5.3 as indicated in the announcement. I also don't get the point of upgrading to the latest angular-cli v1.6 and using it to create the same 5.0.0 app that v1.5 did. Is the way to create a v5.1 ng app is for everyone to manually update all dependencies to ^5.1.0?
- shusson 9y agothe caret ('^') will update a minor version[1]. So ^5.0.0 will install 5.1.0. [1] https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/ https://bytearcher.com/articles/semver-explained-why-theres-...
- mythz 9y agoThe question is what's the best way to create an ng 5.1 app? i.e. what was just announced. I've just manually updated all deps to ^5.1.0.
- shusson 9y agoIf you grab the latest angular-cli and do `ng new foo`, you will get the latest 5.1.0 update. Or if you have an existing app, run `npm install` but make sure you update your package-lock.json file.
- deleted 9y ago[deleted]