nuxt: Getting error caught during app initialization FetchError after updating to Nuxt 3.8.0 (from 3.7.0)

Environment

Operating System: Windows_NT
Node Version: v18.12.1
Nuxt Version: 3.8.0
CLI Version: 3.9.1
Nitro Version: 2.7.1
Package Manager: yarn@1.21.1
Builder: -
User Config: modules, routeRules, runtimeConfig, vueQuery, i18n, css, devServer, components, nitro
Runtime Modules: @hebilicious/vue-query-nuxt @0.2.1, @leanera/nuxt-i18n @0.5.0
Build Modules: -

Reproduction

I cannot provide a reproduction link. Error message: [nuxt] error caught during app initialization FetchError: [GET] “/bk-api/_nuxt/builds/meta/test.json”: 404 Not Found at async $fetch22 (ofetch.js?v=7f011f6e:529:16)

Describe the bug

I got an issue after upgrading to Nuxt 3.8.0 from 3.7.0.

I am using nitro devProxy: nitro: { devProxy: { '/bk-api': { target: 'http://10.1.0.1:8300/bk-api', changeOrigin: true, prependPath: true, } }, },

error error3 error4

Additional context

No response

Logs

No response

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 16 (3 by maintainers)

Commits related to this issue

fix: fixing nuxt to 3.7.4 d/t https://github.com/nuxt/nuxt/issues/23979 — committed to acdh-oeaw/corpsum-ts by ctot-nondef 8 months ago

Most upvoted comments

Still having this issue in 3.10.1

Any help?

dbethel-nib on Feb 9, 2024

I’ve had a similar issue, coming from a different path. (including nuxt as iframe).

Reading the 3.8.0 Release notes helped and disabling the experimental.appManifest feature did it for me:

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  experimental: {
    appManifest: false,
  },
  ...
})

Hope this helps someone. 🙂

ricricucit on Feb 28, 2024

@danielroe Got this same error in nuxt 3.9.1.

zee-shan000 on Jan 15, 2024

@danielroe Got this same error in nuxt 3.10.3. Error 404 /_nuxt/builds/meta/xxxxxxxx.json

jim55167 on Mar 6, 2024

What is the recommended approach to call the API in nuxt3? There are a lot of discussion in issues how to proxy requests to backend and there is nothing in the documentation… I’ve tried several ways and this was the only one that worked with SSR and dev/prod environments. It "will break all kinds of things” only in 3.8 and was working fine from 3.0 to 3.7 Maybe it is a lack of documentation if there are so many misunderstandings and discussions around it.

justserega on Nov 15, 2023