Skip to content

fix(hydration): prevent lazy hydration for updated components #13511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

edison1105
Copy link
Member

@edison1105 edison1105 commented Jun 22, 2025

close #13510

Summary by CodeRabbit

  • Tests

    • Added a new test to verify correct hydration behavior when an async component's props change after parent mount but before the component resolves.
  • Refactor

    • Improved internal handling of async component hydration to better manage state updates and warnings during hydration.

Copy link

coderabbitai bot commented Jun 22, 2025

Walkthrough

The changes introduce a new SSR hydration test for async components and refactor the internal hydration logic in the async component wrapper. The test simulates updating an async component's props before it resolves, while the refactor ensures hydration is skipped if the component has already been patched, logging a warning in development mode.

Changes

File(s) Change Summary
packages/runtime-core/tests/hydration.spec.ts Added a test for updating async component props before resolution during SSR hydration.
packages/runtime-core/src/apiAsyncComponent.ts Refactored internal hydration logic to check for patched state and skip hydration if already patched.

Sequence Diagram(s)

sequenceDiagram
    participant Server
    participant Client
    participant ParentComponent
    participant AsyncComponent

    Server->>Client: Render SSR HTML with async component placeholder
    Client->>ParentComponent: Mounts with toggle=true
    Note over AsyncComponent: Async component not yet resolved
    Client->>ParentComponent: Update toggle=false before async resolves
    AsyncComponent->>Client: Async resolves, hydration begins
    alt Component already patched
        AsyncComponent->>Client: Log warning, skip hydration
    else
        AsyncComponent->>Client: Perform hydration
    end
    Client->>DOM: Update to "Updated async component"
Loading

Assessment against linked issues

Objective Addressed Explanation
Prevent async components with lazy hydration from breaking when interacted with quickly after hydration (#13510)
Ensure hydration skips if async component is already patched (#13510)
Log warning when hydration is skipped due to patched state (#13510)
Add test to verify correct hydration behavior for async components updated before resolution (#13510)

Suggested labels

ready to merge

Poem

A patch for hydration, so sly and neat,
Async awaits, but bugs face defeat!
With warnings and checks, the flow is just right,
No broken UI in the morning light.
🐇✨
Now Vue’s async dance is a joyous sight!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f8314c and 2a74d10.

📒 Files selected for processing (2)
  • packages/runtime-core/__tests__/hydration.spec.ts (1 hunks)
  • packages/runtime-core/src/apiAsyncComponent.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed
🔇 Additional comments (4)
packages/runtime-core/src/apiAsyncComponent.ts (3)

125-126: LGTM! Clean implementation of the patched tracking mechanism.

The use of the beforeUpdate (bu) lifecycle hook to track when the component has been patched is appropriate and ensures the flag is set at the right time in the component lifecycle.


127-137: Excellent implementation of the hydration skip logic.

The performHydrate function correctly:

  • Checks the patched flag before proceeding with hydration
  • Provides a clear warning message in development mode that includes the component name/file
  • Gracefully skips hydration when the component has been updated, preventing potential hydration mismatches

The warning message is informative and will help developers understand why lazy hydration was skipped.


138-147: Clean refactor of the hydration strategy logic.

The conditional assignment of doHydrate maintains the existing behavior while incorporating the new patched component check. When no hydrateStrategy is provided, it now correctly uses performHydrate instead of the raw hydration function.

packages/runtime-core/__tests__/hydration.spec.ts (1)

1163-1224: Excellent comprehensive test for the async component hydration fix.

This test case effectively validates the fix by:

  1. Realistic scenario simulation: Creates an async component with props that change after parent mount but before resolution
  2. Proper async handling: Uses promises and nextTick() to control timing accurately
  3. Comprehensive assertions:
    • Verifies the warning about skipping lazy hydration is logged
    • Ensures no hydration mismatch warnings occur
    • Confirms the final DOM reflects the updated state
  4. Good test structure: Clear setup, execution, and verification phases

The test directly addresses issue #13510 and provides strong regression protection for this edge case.

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

github-actions bot commented Jun 22, 2025

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 101 kB (+6 B) 38.3 kB (+5 B) 34.6 kB (+67 B)
vue.global.prod.js 159 kB (+6 B) 58.5 kB (+2 B) 52 kB (+20 B)

Usages

Name Size Gzip Brotli
createApp (CAPI only) 46.5 kB 18.2 kB 16.7 kB
createApp 54.5 kB 21.2 kB 19.4 kB
createSSRApp 58.7 kB 22.9 kB 20.9 kB
defineCustomElement 59.4 kB 22.8 kB 20.8 kB
overall 68.5 kB 26.4 kB 24 kB

Copy link

pkg-pr-new bot commented Jun 22, 2025

Open in StackBlitz

@vue/compiler-core

npm i https://pkg.pr.new/@vue/compiler-core@13511

@vue/compiler-dom

npm i https://pkg.pr.new/@vue/compiler-dom@13511

@vue/compiler-sfc

npm i https://pkg.pr.new/@vue/compiler-sfc@13511

@vue/compiler-ssr

npm i https://pkg.pr.new/@vue/compiler-ssr@13511

@vue/reactivity

npm i https://pkg.pr.new/@vue/reactivity@13511

@vue/runtime-core

npm i https://pkg.pr.new/@vue/runtime-core@13511

@vue/runtime-dom

npm i https://pkg.pr.new/@vue/runtime-dom@13511

@vue/server-renderer

npm i https://pkg.pr.new/@vue/server-renderer@13511

@vue/shared

npm i https://pkg.pr.new/@vue/shared@13511

vue

npm i https://pkg.pr.new/vue@13511

@vue/compat

npm i https://pkg.pr.new/@vue/compat@13511

commit: 2a74d10

@edison1105 edison1105 added 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope:hydration labels Jun 22, 2025
@edison1105 edison1105 marked this pull request as ready for review June 23, 2025 05:16
@edison1105
Copy link
Member Author

/ecosystem-ci run

@vue-bot
Copy link
Contributor

vue-bot commented Jun 23, 2025

📝 Ran ecosystem CI: Open

suite result latest scheduled
language-tools failure failure
nuxt failure success
primevue success success
pinia success success
radix-vue success failure
test-utils success success
vant success success
router success success
vue-i18n success success
quasar success success
vuetify success success
vite-plugin-vue success success
vueuse success success
vue-simple-compiler success success
vue-macros failure success
vitepress success success

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope:hydration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Async components with lazy hydration break when interacted with very quickly after hydration
2 participants