Building Next: tar: Cannot connect to C: resolve failed
Unanswered
Byte posted this in #help-forum
ByteOP
Hello,
I am trying to build Next.js canary branch.
I'm on a Windows machine.
I believe the building itself is successful.
However, when I try to run:
I get an error:
I use a custom shell but also tried Command Prompt with no issues. My tar binary is the cygwin tar binary.
Any ideas on how to resolve this?
I am trying to build Next.js canary branch.
I'm on a Windows machine.
I believe the building itself is successful.
However, when I try to run:
pnpm pack-next --no-build --releaseI get an error:
Pack C:\Git\next.js/packages/next-swc
> tar -c -f C:\Git\next.js/tarballs/next-swc.tar -- …
tar: Cannot connect to C: resolve failed
C:\Git\next.js\scripts\pack-util.cjs:71
const err = new Error(
^
Error: Command failed with exit code 128: tar -c -f C:\Git\next.js/tarballs/next.tar -- …
at ChildProcess.<anonymous> (C:\Git\next.js\scripts\pack-util.cjs:71:19)
at ChildProcess.emit (node:events:519:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
code: 128,
stdout: Buffer(0) [Uint8Array] [],
stderr: Buffer(41) [Uint8Array] [
116, 97, 114, 58, 32, 67, 97, 110, 110,
111, 116, 32, 99, 111, 110, 110, 101, 99,
116, 32, 116, 111, 32, 67, 58, 32, 114,
101, 115, 111, 108, 118, 101, 32, 102, 97,
105, 108, 101, 100, 10
]
}
Node.js v20.16.0
ELIFECYCLE Command failed with exit code 1.I use a custom shell but also tried Command Prompt with no issues. My tar binary is the cygwin tar binary.
Any ideas on how to resolve this?