Error when using npm link into an angular-cli project
See original GitHub issueCurrently a freshly generated project causes the following error when using npm link
to test the library within a local angular-cli
project;
ERROR in Error encountered resolving symbol values statically. Calling function 'ɵmakeDecorator', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol NgModule in /path/to/project/node_modules/library-name/node_modules/@angular/core/core.d.ts, resolving symbol SampleModule in /path/to/project/node_modules/library-name/index.ts, resolving symbol SampleModule in /path/to/project/node_modules/library-name/index.ts
I’ve dealt with this same problem in a separate library component I have (that does not use this generator) and the solution was to move the @angular/*
dependencies from dependencies
to peerDependencies
in package.json
(as here) as it causes some bizarre errors (I believe in TypeScript). I don’t know if this is something you want to deal with?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top GitHub Comments
@IckleChris — Renaming/removing works as well here as a workaround.
Feel free to let us know if you find a better way, while we search for a solution.
Thanks again!
@caroso1222 — Thank you, much appreciated! 👍