Flex-layout: @angular/[email protected] requires a peer of @angular/[email protected] but none is installed

[akkumar]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

cleaner npm install log

What is the current behavior?

Trying to install and save 2.0.0-beta.10 gives the following warnings.

$ npm install --save @angular/[email protected]

The warnings are below:

npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.

What are the steps to reproduce?

$ npm install --save @angular/[email protected]

gives the following warnings:

npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.

Stackblitz not applicable

What is the use-case or motivation for changing an existing behavior?

cleaner npm install log makes sure we don't overlook other warnings as applicable

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular: 4.4.6
Material: 2.0.0-beta.12
typescript: 2.4.2
OS: linux mint

$ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:    Linux Mint 18.2 Sonya
Release:    18.2
Codename:   sonya

browsers: not applicable.

$ node --version
v8.4.0

$ ng version

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.5.0
Node: 8.4.0
OS: linux x64
Angular: 
...

$ npm version
{ npm: '5.5.1',
  ares: '1.10.1-DEV',
  cldr: '31.0.1',
  http_parser: '2.7.0',
  icu: '59.1',
  modules: '57',
  nghttp2: '1.22.0',
  node: '8.4.0',
  openssl: '1.0.2l',
  tz: '2017b',
  unicode: '9.0',
  uv: '1.13.1',
  v8: '6.0.286.52',
  zlib: '1.2.11' }

Is there anything else we should know?

This issue does not arise in beta.9 though .
This seems to be ok.

 npm install --save @angular/[email protected] @angular/[email protected] @angular/[email protected] [email protected] [email protected]

The following is not, though.

 npm install --save @angular/[email protected] @angular/[email protected] @angular/[email protected] [email protected] [email protected]

[avilao]

I have the same problem.

[ThomasBurleson]

This was a deployment bug.
The release/deployment of v2.0.0-beta.10 has been fixed:

• Peer dependencies updated.
• ReadMe updated with StackBlitz Templates

[ThomasBurleson]

Reopened. We still need to re-deploy to NPM.

[akkumar]

A new release seems to have been released recently that does not have this warning anymore. (it is oddly named , of course - And hopefully that is the inteded release for this fix, i presume).

 npm install --save @angular/[email protected]  @angular/core@~4.4.4 @angular/common@~4.4.4 rxjs@^5.5.0 zone.js@^0.8.4

The above command gives a cleaner log.

[ThomasBurleson]

Fixed with the 2.0.0-beta.12 release. See SHA 62457a5972 and CHANGELOG

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}