Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
NtchPlayer opened this issue Oct 25, 2022 · 9 comments
Open

Comments

@NtchPlayer
Copy link

NtchPlayer commented Oct 25, 2022

Hi,
As @danielroe ask me, I open an issue for error [h3] [unhandled] next is not a function (nuxt/bridge#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-bug-report-h3-rf0rw5

Describe the bug

With this version of nuxt/bridge: 3.0.0-27778050.a725a7a, pwa-module cause this error: [h3] [unhandled] next is not a function when you load your app in a 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.

@SomethingNew71
Copy link

@NtchPlayer any word on getting this merged in to fix this for bridge users?

@emretepedev
Copy link

Same issue here.

@thirdman
Copy link

thirdman commented Jan 7, 2023

pls.

@adamndev
Copy link

adamndev commented Jan 8, 2023

Running into this when installing Nuxt Bridge into a Nuxt 2 application. Tried to create a new Nuxt 2 static site and install Nuxt Bridge into that, but I also ran into the same thing.

Is there a previous working version to try out? Would really like to get this existing application running Bridge so we can begin a migration to Nuxt 3, but seems that PWA/static is our issue. Thanks.

@SomethingNew71
Copy link

This package hasn't been updated in over 2 years now. I have a feeling we won't be getting any response. 😭

@MarcusOhman91
Copy link

Running into this when installing Nuxt Bridge into a Nuxt 2 application. Tried to create a new Nuxt 2 static site and install Nuxt Bridge into that, but I also ran into the same thing.

Is there a previous working version to try out? Would really like to get this existing application running Bridge so we can begin a migration to Nuxt 3, but seems that PWA/static is our issue. Thanks.

I'm in the same situation, it isnt looking very promising though. I think we all have to get an alternate / custom solution to replace this in Nuxt bridge/3.

@dubst3pp4
Copy link

Same error here with nuxt-edge, @nuxt/bridge and @nuxtjs/pwa and static as deployment target.

@SomethingNew71
Copy link

Hey everyone! I am not the maintainer of the original package but it looks like this isn't going to be updated. I decided to fork and create a new npm module off the original code. I haven't got it fully working with nuxt bridge but I think I am close. If anyone in this thread knows what needs to be done to get it fixed please feel free to open a PR and I will get it built and published to NPM so people can continue using PWA functionality with their bridge apps.

@thirdman
Copy link

thirdman commented Apr 1, 2023

Hey everyone! I am not the maintainer of the original package but it looks like this isn't going to be updated. I decided to fork and create a new npm module off the original code.

THANK YOU! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants