angular 2.1.0 release causes missing peer dependencies #2692
Comments
|
When I edit package.json to use angular 2.1.0 (router 3.1.0), I get a working result, but some warning: I'm sure there are things to figure out in terms of the right level of version tolerance for CLI. 2.1.0 shipped yesterday, as the first point minor version release following the exciting new versioning plan for Angular. I would guess that essentially every project in the Angular ecosystem (certainly including all of ours here) has the first opportunity to see how well it works, what sort of version tolerance we can get away with. |
|
I'll take a guess with this - angular-cli requests compiler-cli like this: however, compiler (and everything else) is requested like this: is there a reason that compilier-cli is restricted to the 0.6.x line? |
|
complicated ng' |
|
I updated In my dependencies I have: "dependencies": {
"@angular/compiler-cli": "2.1.0",
"@ngtools/webpack": "1.1.0",
"typescript": "2.0.3", |
|
Also having issues in Ubuntu 16.04 Thanks! |
|
Is there any way to do a npm install -g angular-cli without version 2.1.0 ? can i force an install with a previous angular version? |
|
FWIW, I'm successfully running Angular 2.1.0 in a Angular CLI 1.0.0-beta.17 based project with a few npm warnings; here are my dependencies: |
|
@JanStureNielsen - yes, the npm warnings are what we're interested in, even though the project should work. Does |
|
I was able to resolve this by updating to nodeJS v6 in linux.. and then cache clean and reinstall. |
|
I think this is a possible duplicate for #1941 moreover the the last answer by @JohnMcGuinness fixed issues like this for me, reposting it here for convenience These 5 steps successfully installed |
|
I have the same issue on Ubuntu 16.04 running
package.json |
|
@ninj -- |
|
|
there are WARNs even for angular v2.0.2. To get rid of them, I had to add NOTE: I prefer using repro steps: EDIT: my working dependencies: |
|
#2704 should fix this. More specifically, the |
|
Installing globally the latest angular-cli (beta-18) solved this problem for me. |
|
@filipesilva confirmed fixed - thanks! |
|
i have something strange. my angular-cli versions : and package file: then i changed to rxjs@^5.0.1 what can i do? your help will be appreciated! Thanks |
|
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but non |
|
I am getting this error |
|
Just add and then, npm install. you will see no error. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
OSX + Windows 7
Versions.
Repro steps.
ng initin empty directory, thennpm lsThe log given by the failure.
Mention any other details that might be useful.
I would hope generated projects would have resolvable dependencies so that
npm shrinkwrapworks out of the box.
I imagine there's a way to edit generated pom so that we can use use angular 2.1.0, I'm just not sure what it is...
package.json:
The text was updated successfully, but these errors were encountered: