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

fix(@ngtools/webpack): don't use src dir as a resource #7310

Merged
merged 1 commit into from
Aug 17, 2017

Conversation

filipesilva
Copy link
Contributor

@filipesilva filipesilva commented Aug 9, 2017

We add either src/ or src/$$_gendir/ directories as the lazy route resource, which causes rebuilds whenever anything changes there.

This PR makes it always use the src/$$_gendir/ special directory.

@Brocco this should also fix your local failing poll test.

Fix #6238
Close #6959

@hansl
Copy link
Contributor

hansl commented Aug 9, 2017

The Travis failure seems like a real one to me. What do you think?

@filipesilva
Copy link
Contributor Author

@hansl it was real alright. Seems like a resource is still needed, so I set it to always use the gendir directory.

We add either `src/` or `src/$$_gendir/` directories as the lazy route resource, which causes rebuilds whenever anything changes there.

This PR makes it always use the `src/$$_gendir/` special directory.

@Brocco this should also fix your local failing poll test.

Fix angular#6238
Close angular#6959
@hansl
Copy link
Contributor

hansl commented Aug 11, 2017

I think the genDir directory wouldn't be the right one in JIT mode, correct?

@filipesilva
Copy link
Contributor Author

I don't think it matters actually. We're just telling webpack there's a secret place that's the resource it should watch, but there isn't any path manipulation to be done with it.

@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.

@ngtools/webpack eagerly reloading everything inside of src folder for ng serve
4 participants