-
Notifications
You must be signed in to change notification settings - Fork 12k
Build fail when using npm link to some libraries #3847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I had the same issue, I solved it in this pull request: #3877 |
The problem: duplication of symlinked source files (npm linked sources) in CompilerHost's stats. The solution: resolve these paths before of all Gift of jdavidls
It seems that webpack have reinforced their module webpack/enhanced-resolve. The important point is :
And in angular-cli webpack's configuration there is actually an absolute path :
I've posted #4738 |
hi same issue that don't let me build a project that has son npm linked dependecies. @angular/cli: 1.0.0-rc.1 But sorry @jdavidls @mlardy, i can't understand if you said it's resolved or not... |
#6292 documents how to use linked libraries with the CLI, but relies on changes only present on |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
git clone https://github.com/driftyco/ionic-module-template.git
cd ionic-module-template
npm install
npm run build
(on linux) ornpm run ngc
(on windows since rm does exist on windows)npm link
cd ..
ng new npm-link-test
cd npm-link-test
npm link ionic-module-template
ng build
The log given by the failure.
Here is the output of
ng build
on the real project I work on:Mention any other details that might be useful.
This error does not happen if I
npm pack
the library and install the tarball instead of linking the library.The text was updated successfully, but these errors were encountered: