Upgrading to 3.5.1, crashes the application | Nuxt | Page 1

low lichen May 22, 2023, 7:51 AM

#

Hello, I initially wrote about this issue in the Vue community thinking it may be a Vue internal problem but I am trying here as well in case it is related to Nuxt since I couldn't find an issue on either projects.
(#1109085109379932242 message)

A console warning and an error appears after upgrading Nuxt to 3.5.1.The warning itself suggests it may be a Vue error but in case it is related to Nuxt I am posting it here as well :

ll:376 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core 
  at <NuxtLayout> 
  at <MainApplication key=3 > 
  at <NuxtRoot>
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')
    at parentNode (runtime-dom.esm-bundler.js:33:30)
    at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5777:11)
    at ReactiveEffect.run (null:181:19)
    at instance.update (runtime-core.esm-bundler.js:5814:51)
    at callWithErrorHandling (runtime-core.esm-bundler.js:158:32)
    at flushJobs (runtime-core.esm-bundler.js:357:9)
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'subTree')
    at move (runtime-core.esm-bundler.js:6122:28)
    at move (runtime-core.esm-bundler.js:6122:7)
    at move (runtime-core.esm-bundler.js:6122:7)
    at Object.resolve (runtime-core.esm-bundler.js:1382:11)
    at runtime-core.esm-bundler.js:1505:20

Also the navigations stopped working. Are there any ideas? Should it become an issue in Vue/Nuxt?

white herald May 22, 2023, 1:35 PM

#

I have also experienced this as well. Do you happen to have autoImport off?

white herald May 22, 2023, 2:02 PM

#

@low lichen - something that helped me: I had a component that had a v-if around the root node. Wrapping that in a div fixed the error

low lichen May 22, 2023, 3:14 PM

#

Thank you @white herald for the reply, i will look into either cases tomorrow since i dont remember how it's set up.
I suspect that if there was such a component it would have generated a warning somewhere but I will double check.
Thanks again for your time

dusky idol May 22, 2023, 3:17 PM

#

@low lichen try to delete node_modules and package json

#

do fresh install

#

and test again

opaque haven May 22, 2023, 3:18 PM

#

"npm ci" should do this mostly

low lichen May 22, 2023, 3:20 PM

#

opaque haven "npm ci" should do this mostly

Nice, I didn't know about npm ci, i ll give it a try, thank you both for the suggestions

low lichen May 23, 2023, 8:44 AM

#

I tried to install having removed the lock.json and node modules instead of npm run upgrade but had the same result.
The autoImport isn't changed, it has the default value.
Tried npm ci which crashed, not sure why or how it should be used exactly.

#Upgrading to 3.5.1, crashes the application