workerd fails to run under OpenBSD-current; the afected dependency is install.js #1200
Comments
|
Is it about developing waku itself? Can you try this please? npm create waku@latest |
|
marsbsd-lab01$ npm create waku@latest
✔ Project Name … noveltygen Installing dependencies by running npm install...
✔ Project Name … noveltygen Installing dependencies by running npm install... added 252 packages, and audited 253 packages in 6m 47 packages are looking for funding found 0 vulnerabilities Done. Now run: cd noveltygen marsbsd-lab01$ cd noveltygen
/home/idurando/noveltygen/node_modules/rollup/dist/native.js:89 Error: Your current platform "openbsd" and architecture "x64" combination is not yet supported by the native Rollup build. Please use the WASM build "@rollup/wasm-node" instead. The following platform-architecture combinations are supported: If this is important to you, please consider supporting Rollup to make a native build for your platform and architecture available. Node.js v22.13.1 marsbsd-lab01$ |
|
Thanks! Can you also try npm create vite@latestand select React+TypeScript+SWC? If it works, there's a hope. |
|
marsbsd-lab01$ doas npm create vite@latest
✔ Project name: … noveltygen Scaffolding project in /home/idurando/noveltygen/noveltygen... Done. Now run: cd noveltygen marsbsd-lab01$ cd noveltygen added 140 packages, and audited 141 packages in 2m 40 packages are looking for funding found 0 vulnerabilities
/home/idurando/noveltygen/noveltygen/node_modules/rollup/dist/native.js:89 Error: Your current platform "openbsd" and architecture "x64" combination is not yet supported by the native Rollup build. Please use the WASM build "@rollup/wasm-node" instead. The following platform-architecture combinations are supported: If this is important to you, please consider supporting Rollup to make a native build for your platform and architecture available. Node.js v22.13.1 |
|
Thanks for confirming. I assume that the rollup issue is upstream. If upstream fixes it, Waku should follow. The issue with |
|
My hope was that workerd compatibility wouldn't cause problems unless you are trying to run the cloudflare example. I found a workaround in the nuxt repo that uses package manager overrides to switch to @rollup/wasm-node. Maybe one of those suggestions could work. nuxt/nuxt#24490 |
Running OpenBSD-CURRENT with LATEST NODE and suggested pnpm already. Failed to install dependencies; root cause to be workerd:
doas node install.js
doas (idurando@marsbsd-lab01) password:
node:internal/modules/cjs/loader:1247
throw err;
^
Error: Cannot find module '/home/idurando/noveltygen/install.js'
at Function._resolveFilename (node:internal/modules/cjs/loader:1244:15)
at Function._load (node:internal/modules/cjs/loader:1070:27)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
at node:internal/main/run_main_module:36:49 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
Node.js v22.13.1
The error message indicates that the workerd package does not support the OpenBSD platform. Specifically, the pkgAndSubpathForCurrentPlatform function in the install.js script of the workerd package is throwing an error because it cannot find a precompiled binary for OpenBSD x64 LE (Little Endian). This is a common issue when using Node.js packages that rely on platform-specific native binaries.
Known Information:
Operating System : OpenBSD 7.6.
Node.js Version : v22.13.1.
Package Manager : pnpm.
Error Source : The workerd package's postinstall script fails because it does not have a precompiled binary for OpenBSD.
Repository : You are trying to build the waku repository from GitHub.
Root Cause:
The workerd package is designed to work with specific platforms (e.g., Linux, macOS, Windows) and architectures (e.g., x64). OpenBSD is not officially supported by the package, so the postinstall script fails when it attempts to determine the platform and load the appropriate binary.
The text was updated successfully, but these errors were encountered: