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

Nitro error on fetch.client.js #615

Closed
stephenjason89 opened this issue Nov 6, 2022 · 1 comment
Closed

Nitro error on fetch.client.js #615

stephenjason89 opened this issue Nov 6, 2022 · 1 comment

Comments

@stephenjason89
Copy link

stephenjason89 commented Nov 6, 2022

Environment


  • Operating System: Darwin
  • Node Version: v18.7.0
  • Nuxt Version: 2.16.0-27720022.54e852f
  • Nitro Version: 0.5.4
  • 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-27740081.058a6c1

Reproduction

The error does not happen when
bridge: {
nitro: false,
},

It only occurs when nitro is true

Describe the bug

This error occurs during axios

image

I believe the next errors are related to nuxt/content v1 not working properly with nitro
this is the code that produces these errors
this.$content(this.name).fetch()

With SSR TRUE then i get more errors
image

With SSR FALSE
image

Please let me know if I can provide more info.

Thanks

Additional context

No response

Logs

No response

@github-actions
Copy link
Contributor

This issue was closed because it was open for 7 days without a reproduction.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants