Upgrading with yarn fails...

[bbak]

Log-Entry:

# This file contains the result of Yarn building a package (esbuild@npm:0.25.3)
# Script name: postinstall

node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: C:\Program Files\nodejs\node.exe C:\Users\.....\node_modules\esbuild\bin\esbuild --version
node:child_process:921

    throw err;

    ^



<ref *1> Error: spawnSync C:\Users\...\node_modules\@esbuild\win32-x64\esbuild.exe EPERM

    at Object.spawnSync (node:internal/child_process:1120:20)

    at spawnSync (node:child_process:868:24)

    at Object.execFileSync (node:child_process:911:15)

    at Object.<anonymous> (C:\Users\...\node_modules\esbuild\bin\esbuild:221:28)

    at Module._compile (node:internal/modules/cjs/loader:1734:14)

    at Object..js (node:internal/modules/cjs/loader:1899:10)

    at Module.load (node:internal/modules/cjs/loader:1469:32)

    at Function._load (node:internal/modules/cjs/loader:1286:12)

    at TracingChannel.traceSync (node:diagnostics_channel:322:14)

    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) {

  errno: -4048,

  code: 'EPERM',

  syscall: 'spawnSync C:\\Users\\...\\node_modules\\@esbuild\\win32-x64\\esbuild.exe',

  path: 'C:\\Users\\...\\node_modules\\@esbuild\\win32-x64\\esbuild.exe',

  spawnargs: [ '--version' ],

  error: [Circular *1],

  status: null,

  signal: null,

  output: null,

  pid: 0,

  stdout: undefined,

  stderr: undefined

}



Node.js v23.11.0


    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:882:11)
    at Object.execFileSync (node:child_process:918:15)
    at validateBinaryVersion (C:\Users\...\node_modules\esbuild\install.js:101:28)
    at C:\Users\...\node_modules\esbuild\install.js:283:5 {
  status: 1,
  signal: null,
  output: [
    null,
    Buffer(0) [Uint8Array] [],
    Buffer(1262) [Uint8Array] [
      110, 111, 100, 101,  58,  99, 104, 105, 108, 100,  95, 112,
      114, 111,  99, 101, 115, 115,  58,  57,  50,  49,  13,  10,
       32,  32,  32,  32, 116, 104, 114, 111, 119,  32, 101, 114,
      114,  59,  13,  10,  32,  32,  32,  32,  94,  13,  10,  13,
       10,  60, 114, 101, 102,  32,  42,  49,  62,  32,  69, 114,
      114, 111, 114,  58,  32, 115, 112,  97, 119, 110,  83, 121,
      110,  99,  32,  67,  58,  92,  85, 115, 101, 114, 115,  92,
       73,  53,  53,  53,  52,  53,  52,  92,  79, 110, 101,  68,
      114, 105, 118, 101,
      ... 1162 more items
    ]
  ],
  pid: 39144,
  stdout: Buffer(0) [Uint8Array] [],
  stderr: Buffer(1262) [Uint8Array] [
    110, 111, 100, 101,  58,  99, 104, 105, 108, 100,  95, 112,
    114, 111,  99, 101, 115, 115,  58,  57,  50,  49,  13,  10,
     32,  32,  32,  32, 116, 104, 114, 111, 119,  32, 101, 114,
    114,  59,  13,  10,  32,  32,  32,  32,  94,  13,  10,  13,
     10,  60, 114, 101, 102,  32,  42,  49,  62,  32,  69, 114,
    114, 111, 114,  58,  32, 115, 112,  97, 119, 110,  83, 121,
    110,  99,  32,  67,  58,  92,  85, 115, 101, 114, 115,  92,
     73,  53,  53,  53,  52,  53,  52,  92,  79, 110, 101,  68,
    114, 105, 118, 101,
    ... 1162 more items
  ]
}

Node.js v23.11.0

[evanw]

esbuild.exe EPERM

EPERM is a permission problem, and likely indicates that something is wrong with your specific machine configuration. You have to debug and fix this for yourself.

[jvillanuevabt]

I've been seeing similar EPERM errors on Windows specifically since the 0.25.0 release. For now, I've been pinning to 0.24.2, which is functional, until I have bandwidth to debug. Did something change related to permissions required with that release @evanw?

[evanw]

I don't believe the installer has been changed in a long time.

Unfortunately I don't have a Windows machine and I'm also unfamiliar with Yarn, so I'm unable to debug this for myself. I'll accept a patch for a fix if someone can debug it and provide a fix along with a failing test case.