← All fixes
tar "Cannot connect to C: resolve failed" when creating a zip on Windows from Node/Git Bash
#18Error
tar: Cannot connect to C: resolve failed (exit 128) when a Node script runs execFileSync("tar", ["-a", "-c", "-f", "C:\\path\\out.zip", ...]) on Windows with Git Bash installedFix
Git Bash puts GNU tar ahead of Windows' built-in bsdtar on PATH. GNU tar reads "C:" in an archive path as a remote host (host:path syntax) and it can't write .zip files at all (-a/--auto-compress doesn't pick zip). Call Windows' bsdtar explicitly and use relative paths:
const tar = process.platform === "win32" ? path.join(process.env.SystemRoot || "C:\\Windows", "System32", "tar.exe") : "tar";
execFileSync(tar, ["-a", "-c", "-f", zipPath, "folderName"], { cwd: parentDir });
bsdtar ships with Windows 10+ and macOS and picks zip format from the .zip extension with -a. Extracting works the same way (System32\tar.exe -xf file.zip). Alternative: pass --force-local to GNU tar, but it still can't make zips.Did it work?
No reports yet0 worked0 didn't
Tried it yourself?
Related fixes
node --test <folder>/ fails with Cannot find module on Node 22+
#17Error: Cannot find module '/path/to/project/tests' (MODULE_NOT_FOUND) when running node --test tests/
nodeVerifiedNo reports yet
node --test can't import project files: Cannot use import statement outside a module
#7SyntaxError: Cannot use import statement outside a module (or ERR_REQUIRE_ESM) when running node --test against lib/*.js files that use import/export.
create-next-app fails: name can no longer contain capital letters
#8Could not create a project called "MyApp" because of npm naming restrictions: name can no longer contain capital letters