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
{{ message }}
Repository navigation
Correctly resolve WebPack loaders within npm linked modules #3419
angular-cli: 1.0.0-beta.18
node: 6.9.1
os: darwin x64
Repro steps.
Install NPM linked package that uses a WebPack loader. Loader cannot be resolved.
The log given by the failure.
Module not found: Error: Can't resolve 'style' in '...'
Mention any other details that might be useful.
Merge #2291 was incomplete, in that it does not fully address the issue raised in #1875. It fixes module resolution, but not loader resolution. The following needs to be added to the object returned from getWebpackCommonConfig() in webpack-build-common.ts in order to match current module resolution strategy:
You're right, submitting the CLA is easy enough. It's the internal process of getting an approval for it on my end that's a pain. Again, thanks for making the change. :)
Activity
hansl commentedon Dec 6, 2016
As for the CLA, it's a one time cost that really takes 5 minutes to complete. If you have legal complications I can understand, though.
garkbit commentedon Dec 6, 2016
@hansl, thank you sir.
You're right, submitting the CLA is easy enough. It's the internal process of getting an approval for it on my end that's a pain. Again, thanks for making the change. :)
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.