It's not the node package that's broken, but the esbuild binary distributed on
npm, see also
https://github.com/evanw/esbuild/issues/3523
You might want to try building esbuild yourself, on your OpenBSD system.
On 2024-03-05 10:12, Sandeep Gupta wrote:
As best i can see, node (node-18.18) is broken and cannot be used at all.
No matter the package config "npm install" results in same error:
```
npm install
npm ERR! code 1
npm ERR! path
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! node:internal/errors:865
npm ERR! const err = new Error(message);
npm ERR! ^
npm ERR!
npm ERR! Error: Command failed:
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/bin/esbuild
--version
npm ERR! at checkExecSyncError (node:child_process:890:11)
npm ERR! at Object.execFileSync (node:child_process:926:15)
npm ERR! at validateBinaryVersion
(/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/install.js:99:28)
npm ERR! at
/home/kabiraatmonallabs/Garage/my-skeleton-app/node_modules/esbuild/install.js:286:5
{
npm ERR! status: null,
npm ERR! signal: 'SIGILL',
npm ERR! output: [ null, Buffer(0) [Uint8Array] [], Buffer(0)
[Uint8Array] [] ],
npm ERR! pid: 50423,
npm ERR! stdout: Buffer(0) [Uint8Array] [],
npm ERR! stderr: Buffer(0) [Uint8Array] []
npm ERR! }
npm ERR!
npm ERR! Node.js v18.18.0
```
