-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Cannot read properties of null (reading 'insertBefore') #13766
Comments
Would you try to recreate in https://stackblitz.com/github/nuxt-contrib/vue3-ssr-starter/tree/main first then? |
Do you have one root element? |
Here's an example without Nuxt: https://stackblitz.com/edit/github-tudhv3 - same issue. I think it's an issue with the I'd suggest raising it on |
thanks! |
@danielroe we experienced similar issue with element-plus as well - to be specific with the el-dialog component. The reproduction you made starts working as soon as you remove the parent element of those two spans. I tried to figure out the cause but I have no clue why it starts working as soon as you do this. Working example:
Not working with div or any other grandparent
|
@danekslama That sounds like a vue (or element-plus) bug. See if you can reproduce on https://stackblitz.com/github/nuxt-contrib/vue3-ssr-starter. |
@danielroe after Vue update to 3.4.15 it started working. Unfortunately it still doesn't work on production - same issue in some cases. It is kinda difficult to reproduce now, I will try to discuss the issue elsewhere but it seems that it has been reported many times on element-plus. Hopefully, someone solves it soon. |
Environment
Nuxt project info: 19:20:02
Darwin
v16.14.0
3.0.0-27500344.7fb29b3
yarn@1.22.18
vite
target
,alias
,plugins
,vite
-
-
Reproduction
https://stackblitz.com/edit/nuxt-starter-hfqdfg?file=app.vue
Describe the bug
see
console
in https://nuxt-starter-hfqdfg--3000.local.webcontainer.io/ ,will displayCannot read properties of null (reading 'insertBefore')
not sure this is nuxt bug, i have also found in vue3
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: