feat: peerDependencies and devDependencies auto whitelist.

Type of Issue

[ ] Bug Report
[X] Feature Request

Description

At the moment If I have a package.json like this;

 "peerDependencies": {
    "rxjs": "^5.5.2"
  },
  "devDependencies": {
    "rxjs": "^5.5.2"
  }

I’ll get an error Distributing npm packages with 'devDependencies' is not recommended. Please consider adding rxjs to 'peerDepenencies' or remove it from 'devDependencies'. on/consumers/ng-cli)!_

For development you cannot use peerDependencies as these don’t get installed. I’d expect that if the devDependencies is listed in the peerDependencies I don’t need to add it explicitly in the whitelist. It’s whitelisted automatically.

Expected Behaviour

No error.

Version Information

ng-packagr: 2.3.0

Please include all version numbers that might be relevant, e.g. third-party libraries

[alan-agius4]

@codegagan you can remove the warnings by adding the below to ng-packagr.json, right next to lib property.

Example if the error is related to @angular/package one shall do the the below;

whitelistedNonPeerDependencies: ["angular"] // note: this will be matches as a regexp

If you want to turn off this feature completely you can do the below;

whitelistedNonPeerDependencies: ["."]

[jvanharn]

That is pretty important documentation, maybe add it to the readme and/or changelog? Also add it to the package.schema.json?