You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After going from 1.7.0 to 1.8.0 the prerender now fails. Error: [nuxt] [request error] [unhandled] [500] [nuxt] instance unavailable
here are the relevant logs
at useNuxtApp (./.nuxt/prerender/chunks/build/server.mjs:258:13)
at useRequestEvent (./.nuxt/prerender/chunks/build/server.mjs:796:36)
at prerenderStaticImages (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:22:16)
at getImage2 (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:137:7)
at Object.$img (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:142:12)
at getVariantSrc (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:308:14)
at getSizes (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:249:16)
at $img.getSizes (./.nuxt/prerender/chunks/build/_base-CAUaGNyQ.mjs:153:39)
at ./.nuxt/prerender/chunks/build/NuxtPicture-BHuUH0dC.mjs:45:45
Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.
What will happen?
If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.
If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.
How can I create a reproduction?
We have a template for starting with a minimal reproduction:
After going from 1.7.0 to 1.8.0 the prerender now fails.
Error: [nuxt] [request error] [unhandled] [500] [nuxt] instance unavailable
here are the relevant logs
And the relevant code snippet:
The text was updated successfully, but these errors were encountered: