Repository: angular/flex-layout

Issue #479: @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/core@0.0.0-NG but none is installed
Created: 2017-11-02T11:22:10Z
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/flex-layout@v2.0.0-beta.10
The warnings are below:
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/core@0.0.0-NG but none is installed. You must install peer dependencies yourself.
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/common@0.0.0-NG but none is installed. You must install peer dependencies yourself.
What are the steps to reproduce?
$ npm install --save @angular/flex-layout@v2.0.0-beta.10
gives the following warnings:
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/core@0.0.0-NG but none is installed. You must install peer dependencies yourself.
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/common@0.0.0-NG 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/flex-layout@v2.0.0-beta.9 @angular/core@4.4.6 @angular/common@4.4.6 rxjs@5.5.0 zone.js@0.8.18
The following is not, though.
 npm install --save @angular/flex-layout@v2.0.0-beta.10 @angular/core@4.4.6 @angular/common@4.4.6 rxjs@5.5.0 zone.js@0.8.18

Duplicate issue #475: Bad NPM Install Warning
Created: 2017-11-01T15:20:26Z
Bug
I am getting the following warnings while running npm install:
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/core@0.0.0-NG but none was installed.
npm WARN @angular/flex-layout@2.0.0-beta.10 requires a peer of @angular/common@0.0.0-NG but none was installed.
with the following package.json:
{
  "name": "web",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^4.4.4",
    "@angular/cdk": "2.0.0-beta.12",
    "@angular/common": "^4.4.4",
    "@angular/compiler": "^4.4.4",
    "@angular/core": "^4.4.4",
    "@angular/flex-layout": "2.0.0-beta.10",
    "@angular/forms": "^4.4.4",
    "@angular/http": "^4.4.4",
    "@angular/material": "2.0.0-beta.12",
    "@angular/platform-browser": "^4.4.4",
    "@angular/platform-browser-dynamic": "^4.4.4",
    "@angular/router": "^4.4.4",
    "angular2-notifications": "0.7.7",
    "core-js": "^2.4.1",
    "ng2-dragula": "^1.5.0",
    "rxjs": "^5.4.2",
    "spinkit": "^1.2.5",
    "web-animations-js": "^2.3.1",
    "zone.js": "^0.8.14"
  },
  "devDependencies": {
    "@angular/cli": "1.4.9",
    "@angular/compiler-cli": "^4.4.4",
    "@angular/language-service": "^4.4.4",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "codelyzer": "~3.1.1",
    "hammerjs": "^2.0.8",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~3.2.0",
    "tslint": "~5.7.0",
    "typescript": "~2.3.3"
  }
}

What is the expected behavior?
Considering I am using the same version of angular core and common as beta.10, I would expect no warning. If there are dependency issues however, I would expect the correct component and version to be displayed.

Closing comment (2017-11-04T09:44:11Z): Duplicate of #479.