feat: add perEnvironmentWatchChangeDuringDev
#20996
Merged
+38
−8
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
sapphi-red
added
the
p2-nice-to-have
bluwy
approved these changes
Oct 27, 2025
sapphi-red
deleted the
feat/add-per-environment-watch-change-during-dev
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
watchChangehook was called only for the client environment for backward compat. But there was no way to opt-in to per-environment behavior like we have withperEnvironmentStartEndDuringDev. This PR addsperEnvironmentWatchChangeDuringDevflag to opt-in to the new behavior.Ported the rolldown unrelated part of vitejs#463