Hello, I am not sure why this is occurring but I came across it today, when attempting to build the master commit I get the following error:
docs on main via v19.8.0 on ☁ took 5s
❯ yarn build
yarn run v1.22.19
$ docusaurus build
[INFO] [en] Creating an optimized production build...
✔ Client
● Server █████████████████████████ sealing (88%)
runtime requirements
/usr/bin/node[29853]: ../src/module_wrap.cc:599:v8::MaybeLocal<v8::Promise> node::loader::ImportModuleDynamically(v8::Local<v8::Context>, v8::Local<v8::Data>, v8::Local<v8::Value>, v8::Local<v8::String>, v8::Local<v8::FixedArray>): Assertion `(it) != (env->id_to_function_map.end())' failed.
1: 0x7f032c296e8d node::Abort() [/usr/bin/../lib/libnode.so.111]
2: 0x7f032c2971d6 node::Assert(node::AssertionInfo const&) [/usr/bin/../lib/libnode.so.111]
3: 0x7f032c249a4d [/usr/bin/../lib/libnode.so.111]
4: 0x7f032c7d847a v8::internal::Isolate::RunHostImportModuleDynamicallyCallback(v8::internal::MaybeHandle<v8::internal::Script>, v8::internal::Handle<v8::internal::Object>, v8::internal::MaybeHandle<v8::internal::Object>) [/usr/bin/../lib/libnode.so.111]
5: 0x7f032cc12b18 v8::internal::Runtime_DynamicImportCall(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/../lib/libnode.so.111]
6: 0x7f032c55a5f4 [/usr/bin/../lib/libnode.so.111]
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Robin Shen commented 1 year ago
Looks like something wrong with your environment. It works both inside a docker container, or in my environment.
Unknown commented 1 year ago
Hm,
It might be the nodejs version I am using then!
I am using version 19.8.0, what version are you using to build the docs?
Robin Shen commented 1 year ago
18.12.1
Unknown commented 1 year ago
Ah,
I will try downgrading the node version and see if I still run into a
build failure.
Unknown commented 1 year ago
Ok after downgrading to 18.x it now works, I need to update the onedev-docs aur package (for offline documentation reading) to build using nodejs-lts-hydrogen and not nodejs (19.x unstable)
Hello, I am not sure why this is occurring but I came across it today, when attempting to build the master commit I get the following error: