sometimes I got the following error when building a angular app with nx on the build server.
FATAL ERROR: v8::FromJust Maybe value is Nothing.
1: 00007FF6CA27412F napi_wrap+133311
2: 00007FF6CA20DD06 SSL_get_quiet_shutdown+63062
3: 00007FF6CA20EB9D node::OnFatalError+301
4: 00007FF6CAAD6BB5 v8::V8::FromJustIsNothing+53
5: 00007FF6CA131D2A v8::internal::Isolate::isolate_root_bias+15114
6: 00007FF6CA131BCD v8::internal::Isolate::isolate_root_bias+14765
7: 00007FF6CA12C000 v8::internal::WasmTableObject::WasmTableObject+42832
8: 00007FF6CA2C6002 uv_pipe_pending_type+4242
9: 00007FF6CA2D0AA0 uv_loop_init+1024
10: 00007FF6CA2D0D4A uv_run+202
11: 00007FF6CA14CD3D v8::internal::interpreter::BytecodeLabel::bind+35501
12: 00007FF6CA1487F8 v8::internal::interpreter::BytecodeLabel::bind+17768
13: 00007FF6CA2C152D uv_poll_stop+557
14: 00007FF6CB071860 v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor+146368
15: 00007FFB6EBB84D4 BaseThreadInitThunk+20
16: 00007FFB71511821 RtlUserThreadStart+33
I think it has something todo with the connection because the stack trace is about lib_uv and somewhere it is returning a null where it should return a maybe.
Is this a node bug or has this something todo with angular or nx? This bug was seen with the follow version
Not seen with 18.17.1. But this could also caused by the new build server with more memory and cores
npm cache clean --force
just worked for me.
node - v16.10.0
ng - v12.2.9
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With