feat(watch): new handler option immediate#6484
Merged
johnjenkins merged 6 commits intomainfrom Dec 17, 2025
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
GitHub Issue Number: #6373
It's a regular developer requirement to need
@Watchdecorated methods to fire not only on change, but also during initialisation. At present, devs must do this manually within hooks likeconnectedCallback()What is the new behavior?
By passing
{immediate: true}(e.g.@Watch('propName', {immediate: true})) devs can now fire watch methods during initialisation. The method will fire for class property default values and also incoming values set via initial element attributes / props.There's a slight difference in behaviour from
disttodist-custom-elementsin that because dist-custom-elements components are native elements the watcher will fire for both default class values AND incoming values set via initial element attributes / props, whilst dist components (because they're lazily loaded) will only fire the default class value OR incoming values set via initial element attributes / propsCloses #6373
Documentation
stenciljs/site#1568
Does this introduce a breaking change?
Testing
Other information