Command failed: .../node_modules/@esbuild/linux-loong64/bin/esbuild --version

ZONEZH commented 3 weeks ago

I can download the esbuild dependency normally in both Windows and Mac environments, but it cannot be downloaded in the Linux LoongX64 architecture

Computer configuration: Linux ZONEZH-PC 4.19.0 longson-3 desktop # 5114 SMP Wed May 11 17:37:42 CST 2022 loongarch64 GNU/Linux
Encoding environment: Vue3+vite+tsx...
report errors :

error /home/ZONEZH/code/webledvision/node_modules/esbuild: Command failed.
Exit code: 1
Command: node install.js
Arguments: 
Directory: /home/ZONEZH/code/webledvision/node_modules/esbuild
Output:
node:internal/errors:865
  const err = new Error(message);
              ^

Error: Command failed: /home/ZONEZH/.nvm/versions/node/v18.20.2/bin/node /home/ZONEZH/code/webledvision/node_modules/esbuild/bin/esbuild --version
node:child_process:929
    throw err;
    ^

Error: Command failed: /home/ZONEZH/code/webledvision/node_modules/@esbuild/linux-loong64/bin/esbuild --version
    at checkExecSyncError (node:child_process:890:11)
    at Object.execFileSync (node:child_process:926:15)
    at Object.<anonymous> (/home/ZONEZH/code/webledvision/node_modules/esbuild/bin/esbuild:220:28)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  status: null,
  signal: 'SIGSEGV',
  output: [ null, null, null ],
  pid: 7902,
  stdout: null,
  stderr: null
}

Node.js v18.20.2

    at checkExecSyncError (node:child_process:890:11)
    at Object.execFileSync (node:child_process:926:15)
    at validateBinaryVersion (/home/ZONEZH/code/webledvision/node_modules/esbuild/install.js:100:28)
    at /home/ZONEZH/code/webledvision/node_modules/esbuild/install.js:282:5 {
  status: 1,
  signal: null,
  output: [
    null,
    Buffer(0) [Uint8Array] [],
    Buffer(903) [Uint8Array] [
      110, 111, 100, 101,  58,  99, 104, 105, 108, 100,  95, 112,
      114, 111,  99, 101, 115, 115,  58,  57,  50,  57,  10,  32,
       32,  32,  32, 116, 104, 114, 111, 119,  32, 101, 114, 114,
       59,  10,  32,  32,  32,  32,  94,  10,  10,  69, 114, 114,
      111, 114,  58,  32,  67, 111, 109, 109,  97, 110, 100,  32,
      102,  97, 105, 108, 101, 100,  58,  32,  47, 104, 111, 109,
      101,  47,  90,  79,  78,  69,  90,  72,  47,  99, 111, 100,
      101,  47, 119, 101,  98, 108, 101, 100, 118, 105, 115, 105,
      111, 110,  47, 110,
      ... 803 more items
    ]
  ],
  pid: 7891,
  stdout: Buffer(0) [Uint8Array] [],
  stderr: Buffer(903) [Uint8Array] [
    110, 111, 100, 101,  58,  99, 104, 105, 108, 100,  95, 112,
    114, 111,  99, 101, 115, 115,  58,  57,  50,  57,  10,  32,
     32,  32,  32, 116, 104, 114, 111, 119,  32, 101, 114, 114,
     59,  10,  32,  32,  32,  32,  94,  10,  10,  69, 114, 114,
    111, 114,  58,  32,  67, 111, 109, 109,  97, 110, 100,  32,
    102,  97, 105, 108, 101, 100,  58,  32,  47, 104, 111, 109,
    101,  47,  90,  79,  78,  69,  90,  72,  47,  99, 111, 100,
    101,  47, 119, 101,  98, 108, 101, 100, 118, 105, 115, 105,
    111, 110,  47, 110,
    ... 803 more items
  ]

evanw commented 3 weeks ago

Sorry but there's not much I can do about this. The loong64 version is provided as-is with the assumption that the output of the Go compiler with the settings GOOS=linux and GOARCH=loong64 works on all loong64 devices. Some thoughts:

Does esbuild no longer work at all on any loong64 device? Or is it only working on certain loong64 devices? If it just doesn't work at all, then I can remove it entirely and say that esbuild no longer supports loong64.
Does it work with version 0.21.0 but not version 0.22.0? Version 0.22.0 of esbuild upgraded the version of the Go compiler from Go 1.20 to Go 1.22. It's possible that something about that compiler upgrade broke compilation of Go code to loong64 devices. In that case you'd need to get the Go compiler itself fixed.

ZONEZH commented 3 weeks ago

Sorry but there's not much I can do about this. The loong64 version is provided as-is with the assumption that the output of the Go compiler with the settings GOOS=linux and GOARCH=loong64 works on all loong64 devices. Some thoughts:

Does esbuild no longer work at all on any loong64 device? Or is it only working on certain loong64 devices? If it just doesn't work at all, then I can remove it entirely and say that esbuild no longer supports loong64.

Does it work with version 0.21.0 but not version 0.22.0? Version 0.22.0 of esbuild upgraded the version of the Go compiler from Go 1.20 to Go 1.22. It's possible that something about that compiler upgrade broke compilation of Go code to loong64 devices. In that case you'd need to get the Go compiler itself fixed.

I am glad to receive your reply. Regarding your question:

I currently only have this one in hand, So I am not sure if other Long 64 devices can work properly.
I have seen that the Long community has provided a version of the relevant esbuild https://registry.loongnix.cn:4873/#/detail/@esbuild/linux-loong64 I forcibly changed the esbuild version to the specified version by setting the package's resolutions. I tried 0.21.0, 0.21.5, 0.22.0, and 0.23.0, but still reported the same error

XiaodongLoong commented 1 week ago

Sorry, I have left from Loongson.

ZONEZH commented 1 week ago

Sorry, I have left from Loongson.

Okay, I really don't know what to do with this Loongson architecture. How can I find the corresponding technical support？

evanw / esbuild

Command failed: .../node_modules/@esbuild/linux-loong64/bin/esbuild --version #3822