Angular CLI 1.6.x Peer Dependency Warning from npm

[TheSamsterZA]

Versions

Angular CLI: 1.6.0
Node: 7.10.0
OS: win32 x64
Angular: 5.1.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.0
@angular-devkit/build-optimizer: 0.0.35
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.41
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0
@schematics/angular: 0.1.10
@schematics/schematics: 0.0.10
typescript: 2.4.2
webpack: 3.10.0

Repro steps

1. ng new myapp --routing
2. cd myapp
3. npm list --depth=0

Observed behavior

Step 1 warns with:

npm WARN @schematics/angular@0.1.10 requires a peer of @angular-devkit/schematics@0.0.40 but none is installed.
You must install peer dependencies yourself.

Step 3 errors with:

+-- @angular/animations@5.1.0
+-- @angular/cli@1.6.0
+-- @angular/common@5.1.0
+-- @angular/compiler@5.1.0
+-- @angular/compiler-cli@5.1.0
+-- @angular/core@5.1.0
+-- @angular/forms@5.1.0
+-- @angular/http@5.1.0
+-- @angular/language-service@5.1.0
+-- @angular/platform-browser@5.1.0
+-- @angular/platform-browser-dynamic@5.1.0
+-- @angular/router@5.1.0
+-- @types/jasmine@2.5.54
+-- @types/jasminewd2@2.0.3
+-- @types/node@6.0.92
+-- codelyzer@4.0.1
+-- core-js@2.5.1
+-- jasmine-core@2.6.4
+-- jasmine-spec-reporter@4.1.1
+-- karma@1.7.1
+-- karma-chrome-launcher@2.1.1
+-- karma-cli@1.0.1
+-- karma-coverage-istanbul-reporter@1.3.0
+-- karma-jasmine@1.1.1
+-- karma-jasmine-html-reporter@0.2.2
+-- protractor@5.1.2
+-- rxjs@5.5.5
+-- ts-node@3.2.2
+-- tslint@5.7.0
+-- typescript@2.4.2
`-- zone.js@0.8.18

npm ERR! peer dep missing: @angular-devkit/schematics@0.0.40, required by @schematics/angular@0.1.10

Desired behavior

No peer dependency warnings/errors from npm by using the Angular CLI.

Mention any other details that might be useful (optional)

I get the same warning in step 1 from npm when I install the Angular CLI globally with:

npm i -g @angular/cli

This is detrimental to the first-run experience for new users. Sure, we could ignore the warning, but I'd much prefer it if installing and using the Angular CLI did not throw up things that might cause issues down the line.

[mythz]

This also causes global commands like npm ls -g to throw a "npm ERR! peer dep missing" error.

[whyvrafvr]

Same behaviour running npm update -g.

npm WARN @schematics/angular@0.1.10 requires a peer of @angular-devkit/schematics@0.0.40 but none is installed. You must install peer dependencies yourself.
npm WARN @schematics/schematics@0.0.10 requires a peer of @angular-devkit/schematics@0.0.40 but none is installed. You must install peer dependencies yourself.

npm ERR! code E503
npm ERR! 503 All backends failed or unhealthy: @ngtools/webpack@https://registry.npmjs.org/@ngtools/webpack/-/webpack-1.9.0.tgz

[ibqn]

I am also effected by this when running sudo npm install -g @angular/cli

/usr/lib
└─┬ @angular/cli@1.6.0 
  ├─┬ @angular-devkit/build-optimizer@0.0.35 
  │ ├─┬ loader-utils@1.1.0 
  │ │ ├── big.js@3.2.0 
  │ │ └── emojis-list@2.1.0 
  │ ├── source-map@0.5.7 
  │ └── typescript@2.6.2 
  ├─┬ UNMET PEER DEPENDENCY @angular-devkit/schematics@0.0.41
  │ ├── @angular-devkit/core@0.0.22 
  │ ├── UNMET PEER DEPENDENCY @angular-devkit/schematics@0.0.40
  │ ├── @schematics/schematics@0.0.10 
  │ └── minimist@1.2.0 

[deebloo]

looks like schematics is set as a peerDependency. @clydin was there a reason not to just make it a devDependency?

[ibqn]

similar to issue #8787

[moritz-h]

@deebloo peerDepency is not the problem. I think the problem is by fixing a specific version.
@angular/cli depends on "@angular-devkit/schematics": "~0.0.40" This will currently install 0.0.41.
@schematics/angular and @schematics/schematics has set

"peerDependencies": {
  "@angular-devkit/schematics": "0.0.40"
},

They will not find 0.0.40 and should probably peer depend on the same version @angular/cli depends on.

[GTrebaol]

Is there any workaround for that issue? Installing the dependencies manually doesn't seems to work either.

[moritz-h]

@GTrebaol workaround is just ignore the warning 😄
I should run without problems with 0.0.41. Problem is just that this warning is a little bit annoying but it does not break anything.

[deebloo]

@moritz-h ohhhhhh. thanks makes sense!

[Brocco]

This has been addressed via #8785

[moritz-h]

@Brocco
#8785 does change the minimum version within the @angular/cli dependencies. The warnings are created from the dependencies within @schematics/angular and @schematics/schematics

Will the changes from @angular/cli will be used within the @schematics packages?
I saw the package.json here https://github.com/angular/devkit/blob/master/packages/schematics/angular/package.json with dependency version set to 0.0.0. Also saw the monorepo config: https://github.com/angular/devkit/blob/master/.monorepo.json and wondered where exactly the dependency versions are set.

[titocr]

@moritz-h As @mythz noted, this also causes 'npm ls' to throw an error. This caused our ci job to break, and we'll need to modify it now. Not the end of the world, but you seem to suggest it's a non-issue. It does take real-world dev time to track down the cause of these things.

[moritz-h]

@titocr I never suggested this is a non-issue. Is said the WORKAROUND is just ignore the warning. By not breaking I meant Angular(/CLI) works just fine when 0.0.41 is installed, even if npm complains about missing 0.0.40.
(Actually I thought describing the workaround I found, could save others time by not need to investigate more details about where the warning comes from, while waiting for a fix. 😄 )