* refactor(copy): backport nodejs/node#41351

* perf(copy): parallel copy

* perf(copy): run filter in parallel as well

* Update README.md
* Update LICENSE

* Add promise support for missing fs methods

Fixes #1044

* Try specifying macOS runner explicitly

* Test on more modern Node versions

* Fix tests and note that deprecated constants are not exported

Since nodejs/node#49686, they are not
enumerable properties, so Object.assign doesn't re-export them.
Attempting to directly export them would trigger the deprecation
warning.

Co-authored-by: jayzhai <[email protected]>

…target (#1060)

Fixes #1019
Fixes #1027

Co-authored-by: Claude <[email protected]>
Co-authored-by: mhaynie <[email protected]>

…xists (#1064)

When ensureSymlink is called with a relative srcpath and the destination
symlink already exists, the code was incorrectly resolving the srcpath
relative to cwd instead of relative to the dstpath directory.

This caused ENOENT errors when calling ensureSymlink a second time with
the same relative path, because fs.stat() evaluated the relative path
from the wrong location.

The fix checks if srcpath is relative, and if so, first tries to resolve
it relative to dstpath's directory (standard symlink behavior), falling
back to cwd if that doesn't exist.

Fixes #1038

Co-authored-by: Claude Opus 4.6 <[email protected]>