[h3] [unhandled] next is not a function (Nuxt/Bridge - Nitro 6.0.0)

[NtchPlayer]

Hi, As @danielroe ask me, I open an issue for error [h3] [unhandled] next is not a function (https://github.com/nuxt/bridge/issues/592).

Environment

• Operating System: Darwin
• Node Version: v16.15.0
• Nuxt Version: 2.15.8
• Nitro Version: 0.6.0
• Package Manager: npm@8.19.2
• Builder: webpack
• User Config: telemetry, env, server, nitro, loading, target, head, css, plugins, components, buildModules, modules, auth, oneSignal, fontawesome, i18n, axios, vWave, performance, build, buildDir, dir, webpack, serverHandlers, devServerHandlers, typescript, bridge
• Runtime Modules: @nuxtjs/axios@5.13.6, @nuxtjs/auth-next@5.0.0-1648802546.c9880dc, @nuxtjs/i18n@7.3.0, @nuxtjs/onesignal@3.0.0-beta.16, @nuxtjs/color-mode@3.1.8, v-wave/nuxt
• Build Modules: (), @nuxtjs/eslint-module@3.1.0, nuxt-compress@5.0.0, @nuxtjs/fontawesome@1.1.2, @nuxt/bridge@3.0.0-27778050.a725a7a

Reproduction https://codesandbox.io/s/nuxt-bridge-sitemap-module-bug-report-h3-6mhi80

-> go to sitemap at this url: https://6mhi80.sse.codesandbox.io/sitemap.xml to see the error 500.

Describe the bug

With this version of nuxt/bridge: 3.0.0-27778050.a725a7a, sitemap-module cause this error: [h3] [unhandled] next is not a function when you go the sitemap.xml on your browser.

This warning is also display by the console when the app is compile: WARN [h3] Implicit event handler conversion is deprecated. Use eventHandler() or fromNodeMiddleware() to define event handlers.

This error probably come from nitro 6.0.0, with the last update to unjs/h3.

[lmssieh]

I'm having the same issue, any quick fix for this?

[NtchPlayer]

Nop, I jus't find this repo, a version of this plugin for Nuxt 3 where this bug is corrected: sitemap-module-nuxt-3

[ThomasBerne]

Does anyone here have a solution for nuxt bridge? I can't transfer to nuxt 3 yet and I want to add a sitemap.xml generated by code.

[robinscholz]

Running into this problem as well. Would be great if someone has a workaround!

[katerlouis]

Same problem :'( although it seems to be with Nitro 1.0.0? I simply followed this guide to migrate to nuxt-bridge https://github.com/nuxt/bridge