feat(platform-browser): Warns on conflicting hydration and blocking n… #62963
+48
−6
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
JeanMeche
reviewed
Aug 2, 2025
…avigation Adds an internal token to detect when both hydration and blocking initial navigation are enabled. Logs a warning during app initialization if this unsupported combination is found, helping developers avoid misconfiguration and potential runtime issues.
64e0477 to
52e037e
Compare
|
This PR was merged into the repository by commit 52b8e07. The changes were merged into the following branches: main |
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.
Adds an internal injection token to detect and warn when both hydration and blocking initial navigation are enabled simultaneously.
Since this combination is currently unsupported and may lead to unexpected runtime issues, a warning is now logged during application initialization to alert developers early in the lifecycle.
This helps prevent subtle misconfigurations and aligns with the resolution of #59624
Changes included:
Introduced an internal token to detect the configuration conflict.
Logged a console.warn during app bootstrap when both features are enabled.