-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[ssr] Hydration error with <component :is="someVar"> #3244
Labels
❗ p4-important
Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.
🐞 bug
Something isn't working
scope: ssr
Comments
Add notes here. May need an instance stack: https://github.com/vuejs/vue-next/blob/master/packages/server-renderer/src/render.ts#L146-L158. It is problematic to execute the ssrRender() {
// it's equivalent to calling `ssrRender` recursively
ssrRenderComponent(Comp)
// here, the `currentRenderingInstance` will be `null`
// so resolving component will fail
resolveDynamicComponent(xxx)
} |
HcySunYang
added
the
❗ p4-important
Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.
label
Feb 17, 2021
duplicate of #2863 |
Closed because of duplicate |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
❗ p4-important
Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.
🐞 bug
Something isn't working
scope: ssr
Version
3.0.5
Reproduction link
https://github.com/rstoenescu/vue3-ssr-bug-component-is
Steps to reproduce
Also check terminal output:
<my-x />
from template OR replace it with<div />
. Notice no hydration error.What is expected?
No hydration error.
What is actually happening?
Hydration error when another component is placed as sibling of
<component :is="...">
The text was updated successfully, but these errors were encountered: