fs.copyFile() does not work with /snapshot paths

[TooTallNate]

https://nodejs.org/api/fs.html#fs_fs_copyfile_src_dest_flags_callback

Example error:

{ Error: ENOENT: no such file or directory, copyfile '/snapshot/foo/bar/index.js.map' -> '/Cache/foo/bar/index.js.map'
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '/snapshot/foo/bar/index.js.map',
  dest: '/Cache/foo/bar/index.js.map' }

[jingsam]

I encounter same issue when use fs-extra copySync function. pkg 4.2.6 work fine.

[timsuchanek]

We have the same issue for the prisma CLI.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[github-actions]

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.

[jingsam]

ops！ This issue does't resolve yet

[kamesh95]

@TooTallNate Is there an update on this issue or any workaround? I am still facing this in pkg v5.2.1

[kamesh95]

The same thing happens when using chmod function as well. It says:

ENOENT: no such file or directory, chmod [[PATH_TO_FILE]]

I checked the path using exists function and it returned true that file does exist. But in chmod the same path fails as ENOENT

console.warn("exists:::", fse.existsSync(SCRIPT_PATH));
fse.chmodSync(SCRIPT_PATH, "755");

Output of above lines:

exists::: true
Exception:  
ENOENT: no such file or directory, chmod [[SCRIPT_PATH]]

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[jingsam]

bump

[robertsLando]

It could be because, like for other fs methods, it should be overriden: https://github.com/vercel/pkg/blob/main/prelude/bootstrap.js#L975

And defined here: https://github.com/vercel/pkg/blob/main/prelude/bootstrap.js#L502

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[jingsam]

.

[robertsLando]

@jingsam PR?

[AzazelloB]

The workaround

async function copy(source, target) {
    // use stream pipe to reduce memory usage
    // when loading a large file into memory.
    const writeFileStream = fs.createWriteStream(target);
    const readFileStream = fs.createReadStream(source).pipe(writeFileStream);

    return new Promise(function(resolve, reject) {
        writeFileStream.on('finish', resolve);
        readFileStream.on('error', reject);
    });
}

[AzazelloB]

@jingsam ^

[robertsLando]

I already opened a pr to fix this: #1484

[jesec]

dupe of #420.