-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Bug]: [vue-runtime] TypeError: Cannot read properties of null (reading 'isCE') #43
Comments
Interesting, the library works fine with Vite's SSR and SSG. This seems like a Nuxt 3/Vue Renderer bug, considering the stack trace. |
I wanted to say that I also just got this error when using it with nuxt 3 rc4 (not sure if the previous rc versions have the same issue). |
This is an issue of Nuxt 3, see nuxt/nuxt#13117. |
OK, I am not sure if I did this right, but I added this to my nuxt config: vite: {
logLevel: 'info',
optimizeDeps: {
include: [
'@yeger/vue-masonry-wall'
]
}
}, Unfortunately, I still get the same error above. @or2e Can you let me know if you get this fixed and post the solution here? |
Studied the code of some Nuxt3 modules. Need to add: |
Thank you very much for the workaround! |
I just released v3.0.38 that should fix the issue without requiring the above workaround. |
I'm not sure this issue is correctly solved. I got the same error using "@yeger/vue-masonry-wall": "^3.0.42". I added build: {
transpile: ['@yeger/vue-masonry-wall'],
} to my |
|
I narrowed it down to v3.0.40 of this library. |
Reported upstream at nuxt/nuxt#14375 |
Will be closed by nuxt/nuxt#13632. |
I had the same error using
to |
We now add vue as an external by default. Let me know if this issue still persists. (We can track any remaining issues in nuxt/nuxt#13632.) |
Awesome! I'll close this issue for now. |
Sorry - originally posted thinking this was an issue in nuxt/framework - didn't mean to tell you to close it 😆 |
Description
Reproduction
Nuxt project info: 01:03:48
Linux
v16.14.2
3.0.0-rc.4
3.2.37
[email protected]
vite
The error is only thrown in the production build
Additional context
No response
Preferences
The text was updated successfully, but these errors were encountered: