Environment
- Operating System:
Darwin
- Node Version:
v18.7.0
- Nuxt Version:
2.16.0-27720022.54e852f
- Nitro Version:
0.6.1
- Package Manager:
yarn@3.2.3
- Builder:
webpack
- User Config:
buildDir, srcDir, bridge, components, ssr, dev, alias, image, generate, content, head, typescript, publicRuntimeConfig, privateRuntimeConfig, css, loading, loadingIndicator, plugins, buildModules, modules, proxy, vuetify, build, serverHandlers, devServerHandlers
- Runtime Modules:
@nuxt/content@1.15.1, @nuxtjs/vuetify@1.12.3, @nuxt/image@0.7.1, @nuxtjs/proxy@2.1.0, nuxt-social-meta@1.0.0
- Build Modules:
(), nuxt-storm@1.1.3, nuxt-compress@5.0.0, @pinia/nuxt@0.4.2, @vueuse/nuxt@9.3.0, ~/modules/apolloSSR, @nuxt/bridge@3.0.0-27778503.de9e5c2
Reproduction
After upgrading from
bridge-edge@3.0.0-27699693.0bb392e
to
bridge-edge@3.0.0-27778503.de9e5c2
I am getting errors on
node_modules/nuxi/dist/chunks/index2.mjs
Specifically this line

please note that i am using
bridge: {
nitro: false,
}
Describe the bug

After console logging app, I can see that app doesn't have a property options which causes this error.
Additional context
No response
Logs
No response
Environment
Darwinv18.7.02.16.0-27720022.54e852f0.6.1yarn@3.2.3webpackbuildDir,srcDir,bridge,components,ssr,dev,alias,image,generate,content,head,typescript,publicRuntimeConfig,privateRuntimeConfig,css,loading,loadingIndicator,plugins,buildModules,modules,proxy,vuetify,build,serverHandlers,devServerHandlers@nuxt/content@1.15.1,@nuxtjs/vuetify@1.12.3,@nuxt/image@0.7.1,@nuxtjs/proxy@2.1.0,nuxt-social-meta@1.0.0(),nuxt-storm@1.1.3,nuxt-compress@5.0.0,@pinia/nuxt@0.4.2,@vueuse/nuxt@9.3.0,~/modules/apolloSSR,@nuxt/bridge@3.0.0-27778503.de9e5c2Reproduction
After upgrading from
bridge-edge@3.0.0-27699693.0bb392e
to
bridge-edge@3.0.0-27778503.de9e5c2
I am getting errors on

node_modules/nuxi/dist/chunks/index2.mjs
Specifically this line
please note that i am using
bridge: {
nitro: false,
}
Describe the bug
After console logging app, I can see that app doesn't have a property options which causes this error.
Additional context
No response
Logs
No response