You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
El Capitan 10.11.6
Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.3.1
os: darwin x64
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
checkout git repository
cd into directory
npm link
go to main project
npm install 'linked package'
ng build
If I commit the changes and npm install directly from github repo. everything is working
The log given by the failure. Normally this include a stack trace and some
more information.
null pointer exception when loading RC5 module.
Activity
ghidoz commentedon Sep 4, 2016
Same for me. The solution should be add these lines to the webpack config:
But there is no webpack config that we can edit!
filipesilva commentedon Sep 22, 2016
Would you be willing to submit a PR to add those options?
@TheLarkInn can you have a look at this solution? It's the one listed in http://webpack.github.io/docs/troubleshooting.html#npm-linked-modules-doesn-t-find-their-dependencies
serhiisol commentedon Sep 22, 2016
I've found solution for that and I'll make a pull request ;) hold on guys :)
(#2291)
@filipesilva, @TheLarkInn Could you guys take a look at my PR ? Thanks
fix(#1875): Support npm linked libraries (#2291)
fix(angular#1875): Support npm linked libraries (angular#2291)
fix(#1875): Support npm linked libraries (#2291)
fix(angular#1875): Support npm linked libraries (angular#2291)
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.