Closed MarioC3 closed 4 months ago
Digging a little bit more, I think the bug was introduced on @prismicio/client 7.7.0. When adding some of the hast dependencies.
If I add "@prismicio/client": "7.6.0"
to my resolutions, nuxt starts normally.
Hi @MarioC3, thanks! I'll have a prompt look into it.
Indeed, for now pinning the dependency work as a temporary fix. I'll let you know when we fix it for good (hopefully today)
Hi there,
Once again, thank you so much for reporting this issue and trying out the latest version of our kit!
This should now be fixed in @prismicio/client
v7.7.4, update with:
npm update @prismicio/client
P.S. I'm aware of the warning spam going on about some source map not loading. This appears to be caused by: https://github.com/inikulin/parse5/issues/1194 (also related: https://github.com/nuxt/content/issues/2663), I'll see what I can do about it.
I'm gonna close this issue as everything checked in our QA process. If you still experience the issue with the latest version, you're very welcome to reopen this issue!
Thanks again ๐
Versions
Reproduction
https://stackblitz.com/edit/nuxt-starter-rxtw93 https://stackblitz.com/github/nuxt-modules/prismic/tree/master/examples/minimal?file=pages%2Findex.vue -> Your starter is broken as well.
Steps to reproduce
When starting the Nuxt's environment via
yarn dev
, the server shows a bunch of warnings, and ultimately errors out:What is Expected?
That Nuxt starts normally.
What is actually happening?
Nuxt is erroring out. ๐ญ