feat(@angular/build): enable component template hot replacement by default #29114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
angular-robot
bot
added
detected: feature
clydin
force-pushed
the
hmr/component-hmr-default
branch
6 times, most recently
from
bd1d05a to
66a8add
Compare
…erver SSR To ensure that the Vite-based dev-server SSR uses updated component template update modules, the server module graph is invalidated when component updates are sent. This currently does a full invalidation but in the future this could potentially be optimized to only update the relevant modules. A fix is also present to correct the component update identifier usage to prevent lookup misses.
clydin
force-pushed
the
hmr/component-hmr-default
branch
from
66a8add to
b22d783
Compare
…fault When using the `application` builder (default for new projects) with the development server, component template only changes will now automatically replace the template within the running application without a full reload of the page. No application code changes are necessary and both file-based (`templateUrl`) and inline (`template`) component templates are supported. Additionally, changing a components styles in combination with a template change is also supported for hot replacement. This includes both inline and file-based changes. If any issues are encountered or it is preferred to not hot replace component templates, the `NG_HMR_TEMPLATES=0` environment variable can be used to disable the feature. Setting the `liveReload` option or `hmr` option to false will also disable all updates.
clydin
force-pushed
the
hmr/component-hmr-default
branch
from
b22d783 to
aa27741
Compare
clydin
added
the
action: review
alan-agius4
added
action: merge
|
🎉 |
Merged
2 tasks
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
When using the
applicationbuilder (default for new projects) with the development server, component template only changes will now automatically replace the template within the running application without a full reload of the page. No application code changes are necessary and both file-based (templateUrl) and inline (template) component templates are supported. Additionally, changing a components styles in combination with a template change is also supported for hot replacement. This includes both inline and file-based changes.If any issues are encountered or it is preferred to not hot replace component templates, the
NG_HMR_TEMPLATES=0environment variable can be used to disable the feature. Setting theliveReloadoption orhmroption to false will also disable all updates.