Closed PawFV closed 2 years ago
Hey @PawFV
Thanks for the detailed issue! Looks like an issue with the nuxt kit the package was using. I've migrated this package to nuxt-module-builder and cleaned up a few things which should resolve this issue.
Can you try with 0.4.3 and let me know if you still have issues.
Thanks
@harlan-zw hey updated the package but the probleme persists, I'm having the exact same error.
As it might be really hard to replicate (I'm working with a huge Nuxt app) we can go to a debugging session in my env if you like, just lmk anything I can do, if this module works as I think it works it will solve a lot of problems we have currently because of huge hydration.
Even with a lot of techniques like lazy-loading 3rd party, optimizing plugins, lazy hydrate and so on we still can't get a good lighthouse score on mobile, half of our bundle size LH say's it's unused, we can't technically remove GRAPHQL from our bundle, idk what the hell is that metric but anyways...
Hmm it seems like something specific to your project. I've again tried to replicate it without success here: https://stackblitz.com/edit/nuxt-starter-9vbury?file=nuxt.config.js
Could you try:
npm why unctx
npm why @nuxt/kit
@harlan-zw Sorry for the delay!
# npm why unctx
unctx@0.0.3
node_modules/unctx
unctx@"^0.0.3" from @nuxt/kit@0.6.4
node_modules/@nuxt/kit
@nuxt/kit@"0.6.4" from @bravadoco/nuxt-timings@0.1.33
node_modules/@bravadoco/nuxt-timings
@bravadoco/nuxt-timings@"^0.1.33" from the root project
# npm why @nuxt/kit
@nuxt/kit@0.6.4
node_modules/@nuxt/kit
@nuxt/kit@"0.6.4" from @bravadoco/nuxt-timings@0.1.33
node_modules/@bravadoco/nuxt-timings
@bravadoco/nuxt-timings@"^0.1.33" from the root project
Hey @PawFV, I've pushed an update for the package to use the latest RC of @nuxt/kit. If that doesn't solve it you may need to try removing the module @bravadoco/nuxt-timings from your package.json and re-install deps.
Seems as though it's locked @nuxt/kit and unctx to a very early version.
That's my best guess as to the issue, if that doesn't solve it, please feel free to re-open this issue
Describe the bug When
yarn build
error happens at the very beggining of the build.I logged debugged
nuxtCtx
and it seems like it only gets this properties inside the objectI'm not so familiar with
unctx
but replacingwhile importing
createContext
bypasses the error but tbh I'm just shooting in the dark and just playing a bit, I lack context literally speaking.Nuxt:
My
package.json
If I can do anything else to fix the issue or any more context you may need just tell me, thanks!