When I use github codeaction to rebuild my package, `Error: EISDIR: illegal operation on a directory, lstat 'D:'` occurs

[zpcalan]

Version

v22.21.1

Platform

windows

Subsystem

No response

What steps will reproduce the bug?

Use codeaction to trigger prebuild.yml of my project.
For node v18 and v20, it's all good.

How often does it reproduce? Is there a required condition?

Every time I ran prebuild for v22 and above.

What is the expected behavior? Why is that the expected behavior?

Prebuild successfully.

What do you see instead?

The log:

=== DEBUG: Execution Attempt ===
Attempting to execute: node node_modules\tree-sitter-cli\cli.js generate
Working directory for execution: D:\a\tree-sitter-arkts\tree-sitter-arkts
--- Trying Method 1: npx tree-sitter generate ---
node:fs:2744
    const out = binding.lstat(base, false, undefined, true /* throwIfNoEntry */);
                        ^
Error: EISDIR: illegal operation on a directory, lstat 'D:'
    at Object.realpathSync (node:fs:2744:25)
    at toRealPath (node:internal/modules/helpers:61:13)
    at Function._findPath (node:internal/modules/cjs/loader:733:24)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1369:27)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)
    at Function._load (node:internal/modules/cjs/loader:1192:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
    at Module.require (node:internal/modules/cjs/loader:1463:12) {
  errno: -4068,
  code: 'EISDIR',
  syscall: 'lstat',
  path: 'D:'
}
Node.js v22.21.1
Node process exited with status 1

I search for many methods trying to fix this issue but none of them takes effect. Please give me some advice of how to fix this bug. Thank you so much!!

Additional information

No response

[zpcalan]

My path is D:\a\tree-sitter-arkts\tree-sitter-arkts and is not long enough, so that this issue does not apply to my scenario.

[DoubleClickPreferred]

Hello @zpcalan , I had this issue as well.

Check if your path is just an absolute path or a DOS device path like \\?\D:\a\tree-sitter-arkts\tree-sitter-arkts

Node v20 manages these DOS device paths correctly.
Node v22 and v24 do not anymore.

Note: I'm launching node from a Bash script with a command like node $BASE_PATH/foo/bar/my-script.mjs. Now, I use the ability to remove the prefix of the parameter-expansion operation: ${BASE_PATH#\\\\?\\}/foo/bar/my-script.mjs.

[johncrim]

This is still a severe problem for Windows developers. It looks like the bug occurred with the removal of permission checks here:

51f4ff2

This bug has a fix, but unfortunately there are some lines changing HTTP behavior that were mixed in and never removed. So the PR has been sitting for 8 months:

Another PR with related fixes:
#62639