Danian

I can't reproduce this anymore with 0.18.3, Vite 5.4.10 and: ``` - Operating System: `Darwin` - Node Version: `v20.17.0` - Nuxt Version: `3.13.2` - CLI Version: `3.15.0` - Nitro Version:...

I'm also having this issue, no clue how to fix. It only seems to happen with images I built myself? Running it inside a common `node:20` image works, for example....

@danielroe > Is there anything you want to do that isn't currently possible? I am currently using nuxt's `nitro.errorHandler` config option to transform my error responses and normalize all errors...

> Maybe you can try this solution: **server/api/[...].ts** > > ```ts > export default defineEventHandler(async (event) => { > throw createError({ > statusCode: 404, > message: "404 Not Found", >...

> @daniandl Sorry, I re-checked the documentation and tried to implement it like this: **/server/plugins/error.ts** > > ```ts > export default defineNitroPlugin((nitroApp) => { > nitroApp.hooks.hook("error", (error, { event })...

> It works pretty well but I am not sure whether there are side effects using this approach. 🤔 Thanks for sharing, but like danialroe said in 1st post, it...

> ``` > export default defineNitroPlugin((nitroApp: any) => { > nitroApp.hooks.hook('render:response', (response: any) => { > response.body = response.body.replaceAll('/_nuxt/\0', '/_nuxt/') > }) > }) > ``` You can add `RenderResponse`...

> I am open to the idea and slowly leaning towards it. Would have to be part of v4, which probably will be early next year Could you make a...