warn for missing dependencies

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

With unbundled dependencies library projects must list their dependencies both in the root package.json and in project/<project-name>/package.json as either regular dependencies or peerDependencies. However if a dependency is only listed in the root package.json the library will build without error and the issue will only manifest when the library is included in another project which is likely after the library has already been published.

Expected Behaviour

When building a library project ng-packagr should error or warn when it detects an import that can’t be matched to a project file or an entry in project/<project-name>/package.json.

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr: 9.1.5
@angular/*: 9.1.13
typescript: 3.8.3
rxjs: 6.6.3
node: 12.20.1
npm/yarn: 6.14.10

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

[alan-agius4]

I think since this functionality is already provided by packages in the toolchain, such as ESLint and TSLInt, we shouldn’t re-invent the wheel.

Let’s reconsider this in the future if we see that is a greater demand for this.

[github-actions[bot]]

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

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