Plugins are triggered and previous context is lost on error shown about nuxt HOT 5 CLOSED

Basically, any thrown error inside defineRenderHandler leads to this.

from nuxt.

As I've struggled deep into the code, the problem is probably that we can't rerender our app if any error happened.

The only thing that could delay some component from rendering is onServerPrefetch, but we can't wait inside of it forever since we can't know if remaining app has been rendered or not.

Solution could be is to listen for @resolve hook for that, but this is currently impossible due to vuejs/core#8555 not merged.

Also solution could be to render app twice (don't use Nitro's error handler) and on second render pass all the payload and state to this second render, and that will also skip mounting any plugins twice there. But I don't know if it is possible to preserve context somehow for multiple renders.

UPD: probably possible to restore state using useSSRContext().

from nuxt.

Yes, that is the case (and intentional). To render an error page, we render the app a second time, but just the error page and not app.vue.

Plugins might do more things than set payload/state, such as inject helper functions. So we do need to rerun them. You can add your own logic to avoid rerunning logic. You can check in your plugins if useError().value is set.

from nuxt.

Yes, that is the case (and intentional). To render an error page, we render the app a second time, but just the error page and not app.vue.

Plugins might do more things than set payload/state, such as inject helper functions. So we do need to rerun them. You can add your own logic to avoid rerunning logic. You can check in your plugins if useError().value is set.

Yes I could, but sadly pinia context is lost as well :(

So I have to refetch for my data

from nuxt.

@danielroe do you think this worth trying to solve when @resolve on Suspense will be supported on SSR? Basically, that's how it worked in Nuxt 2 (I know that there was totally different logic).

If at least state (including useState & pinia) would be passed to this reloaded context, it wouldn't be such a problem.

from nuxt.