Skip to content

fix(@ngtools/webpack): Race condition between invalidate & populateWebpackResolver #6920

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

Conversation

scott-phillips-sp
Copy link

No description provided.

@hansl
Copy link
Contributor

hansl commented Jul 17, 2017

Hey @scott-phillips-sp, could you rebase your changes on top of master? We reworked the way our travis tests are run and it might help.

I don't see a problem with this PR.

@ItsMeDelanoDev
Copy link

Can this be picked up? This is really annoying while using webpack --watch.

@hansl hansl removed their assignment Feb 8, 2018
@clydin
Copy link
Member

clydin commented Feb 23, 2018

Since populateWebpackResolver no longer exists, this should no longer be necessary.

@clydin clydin closed this Feb 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.

5 participants