nuxt: FATAL ERROR: v8::FromJust Maybe value is Nothing.
Environment
- Operating System:
Linux - Node Version:
v14.18.1 - Nuxt Version:
3-3.0.0-27234368.47ea41d - Package Manager:
Yarn - Bundler:
Webpack - User Config:
- - Runtime Modules:
- - Build Modules:
-
Steps to reproduce
- Install a fresh Nuxt 3
- Delete app.vue
- Run
yarn dev -o - Create ./pages directory
- See error
ℹ Directory pages/ created. Restarting nuxt... 21:24:20
FATAL ERROR: v8::FromJust Maybe value is Nothing.
1: 0xa389b0 node::Abort() [/usr/local/bin/node]
2: 0x96e0af node::FatalError(char const*, char const*) [/usr/local/bin/node]
3: 0xbb773a v8::Utils::ReportApiFailure(char const*, char const*) [/usr/local/bin/node]
4: 0xa3c19d node::fs::FileHandle::CloseReq::Resolve() [/usr/local/bin/node]
5: 0xa3c2f9 [/usr/local/bin/node]
6: 0x13b992d [/usr/local/bin/node]
7: 0x13be0b6 [/usr/local/bin/node]
8: 0x13d0524 [/usr/local/bin/node]
9: 0x13be9e8 uv_run [/usr/local/bin/node]
10: 0xafab43 node::worker::Worker::Run() [/usr/local/bin/node]
11: 0xafb5f8 [/usr/local/bin/node]
12: 0x7f176d5e5609 [/lib/x86_64-linux-gnu/libpthread.so.0]
13: 0x7f176d50c293 clone [/lib/x86_64-linux-gnu/libc.so.6]
Aborted (core dumped)
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Expected behaviour
Restart Nuxt without error.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 11
- Comments: 32 (14 by maintainers)
I also encounter a similar issue with @nuxt/bridge:
Nuxi report:
I don’t have a proper way to replicate this error as this spawns randomly while coding in the project.
The last time I had it was when editing a plugin, the replacement made the server crash.
Edit for additional context:
node_modulesand reinstall everything so it boots up again.Alright, made a reproduction without
@nuxt/contentv2: https://github.com/Atinux/nuxt-maybe-value-reproYou will need to save faster and more times the
~/plugins/foo.tsbecause I did not add any parsing logic in it, but basically it is related to memory usage.Hello, in a somehow consistent project, we encounter a similar issue. Sometimes it happens just right after starting the dev server !
Nuxt3 v3.0.0-27420403.16e2a54 Issue observed on MacOS I cannot get a minimal reproduction…
@danielroe
Here’s the minimal reproduction I got for this issue : https://github.com/kevinmarrec/nuxt-maybe-value-repro
@nevadavid ; @bambo0cha ; @productdevbook ;
Do you guys have an idea on how to replicate this issue in a sandboxed environment ?
And how to get it 100% of the time ?
I think it would help @danielroe and @pi0 debugging this.
I tried to replicate it in my own contexts, but I fail getting a reproduction that hits this bug every time in the same place.
Yes, that’s very helpful, thanks for the link and some causes of this.
Haven’t updated this in a while but this error is a node bug and almost always conceals an underlying error/issue. So it is not necessarily attributable to an issue in Nuxt or indeed any one issue at all.
Tracking this in https://github.com/nodejs/node/issues/6899
The following might help some of you using vite https://github.com/nodejs/node/issues/6899#issuecomment-1210954352
Could you try with this option in your
nuxt.config:Just came across this. Deleting the
.nuxtfolder fixed it for me!Edit: it did not. But going from
"nuxt": "npm:nuxt3@latest"to"nuxt": "3.0.0-rc.2"seems to workThanks, @kevinmarrec for making smaller repro I will also try it. However by minimal, we need a repro without dependency on any nuxt module (yours is using content v2 which likely makes it more complicated to find a root cause)
Hey @Tahul 😃 I still get this error with Nuxt Bridge. The server and client-side are compiled successfully but crash as soon as Nuxt starts.
Our codebase is quite large but we are using Node
v14.17.6and we followed the guideline from the documentation.