vercel / pkg

Package your Node.js project into an executable
https://npmjs.com/pkg
MIT License
24.33k stars 1.02k forks source link

internal spawnSync error? #1908

Closed ahmdmoadi closed 1 year ago

ahmdmoadi commented 1 year ago

i ran pkg --target latest-win-x85

pkg@5.8.1 Fetching base Node.js binaries to PKG_CACHE_PATH

Error! 404: Not Found Not found in remote cache: {"tag":"v3.4","name":"node-v18.5.0-win-x86"} Building base binary from source: built-v18.5.0-win-x86 Fetching Node.js source archive from nodejs.org... Extracting Node.js source archive...

deps/ deps/cares/ deps/cares/msvc_ver.inc deps/cares/config.guess deps/cares/acinclude.m4 deps/cares/TODO ... test/pseudo-tty/readline-dumb-tty.out test/pseudo-tty/test-trace-sigint-on-idle.js test/pseudo-tty/test-tty-stdout-end.js README.md configure.py node.gypi CONTRIBUTING.md .clang-format vcbuild.bat Applying patches Error! Error: spawnSync patch ENOENT at Object.spawnSync (node:internal/child_process:1110:20) at spawnSync (node:child_process:871:24) at C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:148:51 at step (C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:33:23) at Object.next (C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:14:53) at C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:8:71 at new Promise () at __awaiter (C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:4:12) at spawn (C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\utils.js:145:12) at C:\Users\Admin\Desktop\data\app\node_modules\pkg-fetch\lib-es5\build.js:221:60

and it exited. here is the log file:

out.log

is it that pkg doesn't support x86 or what??

github-actions[bot] commented 1 year ago

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[bot] commented 1 year ago

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