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
Related to #31 because it's the same error, but not because useTranslation is called in request hook.
Deploy the reproduction to Vercel and put a ping on it.
I have got uptime kuma calling /api/webhook endpoint every minute. Works fine for about 2 hours and then suddenly
[nuxt] [request error] [unhandled] [500] middleware not initialized, please setup `onRequest` and `onAfterResponse` options of `createApp` with the middleware obtained with `defineI18nMiddleware`
Could be a nuxt/i18n issue.
Edit: no issue on Cloudflare, where I also deployed the same reproduction.
The error can also be thrown just after deployment.
My guess would be that the order in which plugin/middleware/eventhandler get executed isn't correct.
So I would assume it has something to do with cold start and the order of the i18n middleware that is running AFTER the request is being handled.
Log of failed request:
"onRequest" comes AFTER "webhook entered"
Describe the bug
Related to #31 because it's the same error, but not because
useTranslation
is called inrequest
hook.Deploy the reproduction to Vercel and put a ping on it.
I have got uptime kuma calling /api/webhook endpoint every minute. Works fine for about 2 hours and then suddenly
Could be a nuxt/i18n issue.
Edit: no issue on Cloudflare, where I also deployed the same reproduction.
Reproduction
https://github.com/DavidDeSloovere/nuxt-i18n-nitro-issue31
Deploy to Vercel. Call /api/webhook.
System Info
Deployed on Vercel. With Node 22.x
Used Package Manager
pnpm
Additional context
The error can also be thrown just after deployment.
My guess would be that the order in which plugin/middleware/eventhandler get executed isn't correct.
So I would assume it has something to do with cold start and the order of the i18n middleware that is running AFTER the request is being handled.
Log of failed request:

"onRequest" comes AFTER "webhook entered"
Log of working request:
Validations
The text was updated successfully, but these errors were encountered: