Skip to content
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

Merged
merged 2 commits into from
Jul 27, 2017
Merged

Conversation

filipesilva
Copy link
Contributor

@filipesilva filipesilva commented Jul 27, 2017

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:

  • it's affecting a lot of users.
  • the real solution is non-trivial.

@filipesilva filipesilva requested a review from hansl as a code owner July 27, 2017 15:03
@alxhub alxhub merged commit 3baba67 into angular:master Jul 27, 2017
@filipesilva filipesilva deleted the support-enhanced-resolve branch July 27, 2017 15:58
filipesilva added a commit that referenced this pull request Jul 27, 2017
* fix(@ngtools/webpack): support [email protected]

Followup to #7123

* fix(@angular/cli): unpin webpack 3.3.0

Followup to #7130
filipesilva added a commit that referenced this pull request Jul 27, 2017
* fix(@ngtools/webpack): support [email protected]

Followup to #7123

* fix(@angular/cli): unpin webpack 3.3.0

Followup to #7130
@burtonjc
Copy link

@filipesilva 👋 , thank you for your responsiveness on this. Made a world of difference for our team!

@filipesilva filipesilva mentioned this pull request Jul 28, 2017
@filipesilva
Copy link
Contributor Author

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!

filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 22, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 22, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 22, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 22, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 23, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 23, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this pull request Aug 23, 2017
hansl pushed a commit that referenced this pull request Aug 23, 2017
hansl pushed a commit that referenced this pull request Aug 25, 2017
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this pull request Apr 23, 2018
* fix(@ngtools/webpack): support [email protected]

Followup to angular#7123

* fix(@angular/cli): unpin webpack 3.3.0

Followup to angular#7130
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this pull request Apr 23, 2018
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants