The command fails on Windows with an error similar to: tar: Error opening archive: Failed to open 'D:\...\tarballs\next.tar'

TL;DR

The issue can be fixed by modifying the unpack-next.ts script to use double quotes instead of single quotes for paths on Windows.

Guidance

• The error occurs because Windows' built-in tar.exe treats single-quoted paths as literal characters, causing the tarball to not be found.
• To verify the issue, run the pnpm unpack-next command on a Windows machine and check for the error message indicating that the tarball cannot be found.
• A potential workaround is to modify the unpack-next.ts script to use double quotes for paths on Windows, similar to how POSIX systems handle double quotes.
• The unpack-next.ts script should be updated to handle the difference in path quoting between Windows and POSIX systems.

Example

// In unpack-next.ts, update the tar command to use double quotes on Windows
const tarCommand = process.platform === 'win32' ? `tar -xvf "${tarballPath}"` : `tar -xvf '${tarballPath}'`;

Notes

This fix assumes that the issue is solely due to the difference in path quoting between Windows and POSIX systems. If other issues are present, additional modifications may be necessary.

Recommendation

Apply workaround: The best course of action is to update the unpack-next.ts script to handle the difference in path quoting between Windows and POSIX systems, as this will allow the pnpm unpack-next command to work correctly on both platforms.