-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Support enhanced resolve #7169
Support enhanced resolve #7169
Conversation
* fix(@ngtools/webpack): support [email protected] Followup to #7123 * fix(@angular/cli): unpin webpack 3.3.0 Followup to #7130
* fix(@ngtools/webpack): support [email protected] Followup to #7123 * fix(@angular/cli): unpin webpack 3.3.0 Followup to #7130
@filipesilva 👋 , thank you for your responsiveness on this. Made a world of difference for our team! |
Hey @burtonjc, just wanted to say it makes me really happy to hear that! It's obviously important to me that our stuff is working correctly and fulfilling it's purpose, but comments like yours never fail to put a happy smile on my face and leaving me feeling good for a fair bit. Cheers! |
* fix(@ngtools/webpack): support [email protected] Followup to angular#7123 * fix(@angular/cli): unpin webpack 3.3.0 Followup to angular#7130
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. |
This is a temporary hack to address these two issues:
This way we set values correctly in both a Map (enhanced-resove>=3.4.0) and object (enhanced-resolve >= 3.1.0 <3.4.0).
The right solution is to create a virtual filesystem by decorating the filesystem, instead of injecting data into the private cache of the filesystem.
Doing it the right way should fix other related bugs, but meanwhile we hack it since: