Error on clear installation nuxt. | Nuxt | Page 1

#

Hi @mild coral. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

This exact error is a known Nuxt 4.3.0 / @nuxt/[email protected] issue that appears on a fresh install when requesting /_nuxt/. The stack trace and [CAUSE] { status: 404 } you see matches the reports here. [v4.3.0 Bun/pnpm]

From the linked issue, users report:

The error happens right after upgrading/creating a project with Nuxt 4.3.0.
It’s triggered by a 404 on /_nuxt/ in dev, then createError in the CLI blows up. [v4.3.0 Bun/pnpm]
Downgrading Nuxt to an earlier 4.x version (e.g. 4.1.2) avoids the problem. [Install fails 4.2.2]

Given what’s in the sources, the only concrete, confirmed workaround is:

Pin Nuxt to a previous 4.x version that is known to work, for example 4.1.2:

Change your package.json:

{
  "devDependencies": {
    "nuxt": "4.1.2"
  }
}

Then remove lockfile and node_modules and reinstall:

rm -rf node_modules package-lock.json pnpm-lock.yaml yarn.lock
npm install   # or pnpm install / yarn install
npm run dev

If you use pnpm, you can also try pnpm dedupe to clean up peer-dependency mismatches (this helped with another Nuxt 4.x “Cannot read properties of null (reading 'ce')” report). [Cannot read 'ce']

#

The knowledge sources don’t show a final upstream fix or a specific configuration change you can apply in 4.3.0 itself, only that the problem is tied to the current CLI and that downgrading Nuxt/CLI resolves it for affected users. If you need to stay on 4.3.0, the sources don’t provide a reliable workaround beyond that.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@mild coral Kapa.ai is still learning and improving, please let me know how I did by reacting below.

#Error on clear installation nuxt.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: