this.$nuxt.error() causes error.vue to render incorrectly (using fetch >= 2.12)

[rmirabelle]

I'm still trying to wrap my head around the nearly insurmountably confusing usage of fetch() and its impact on error.vue

My current understanding is that error.vue is always rendered as either a Component or a Page, but never a Layout.
Already confusing.

Old fetch and throw new Error act like they're supposed to:

If I call the 'old' (< 2.12) version of fetch, with a context argument, then call context.error('whatever'), OR if I simply throw new Error('whatever'), error.vue is rendered as expected - a Page, whose layout property is properly respected.

New fetch does what??

If I call the new (>= 2.12) version of fetch() with no arguments, then call this.$nuxt.error('whatever'), error.vue appears to be forcibly rendered INLINE as a Component that completely ignores its own layout property and renders inside the current layout instead.

I assume this is a bug in this.$nuxt.error()?

Surely, this can't be the expected behavior, i.e. completely changing the way error.vue is rendered based solely on the this context that new fetch provides?

[asmeeee]

This was reported in #7567 and is supposed to be fixed by #7654, but I still encounter a similar scenario.

[minawalphonce]

Not fixed in 2.13.3 related #7743

[stale]

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.

[bpeab]

Still an issue, the stalebot shouldn't close it.