This repository was archived by the owner on Aug 7, 2021. It is now read-only.
fix(Angular): add hot loader for lazy loaded NgModules #747
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the current behavior?
In NativeScript Angular the hot updates are only accepted in the entry file (
main.ts
). The lazy loaded NgModules are not directly imported anywhere in the dependency graph with rootmain.ts
. That's why the hot updates in lazy modules don't bubble up to the accept inmain.ts
and HMR doesn't work in lazy modules.What is the new behavior?
Every lazy loaded NgModule is augmented with HMR self-accept during build by the
lazy-ngmodule-hot-loader
.fixes NativeScript/nativescript-angular#1564
BREAKING CHANGES:
The
lazy-ngmodule-hot-loader
should be added to the webpack configuration.BEFORE
AFTER