search

vercel / pkg

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

Failed to specify local node.js cache #1988

Closed kerwenzhang closed 9 months ago

kerwenzhang commented 1 year ago

Discussed in https://github.com/vercel/pkg/discussions/1986

Originally posted by **kerwenzhang** September 6, 2023 My node project is compiled using node.js v18.14.0 x86. When using pkg to package the output, I want to use the local node binaries which was compiled by myself. Is there a good way to achieve this? I added two system environment: ![image](https://github.com/vercel/pkg/assets/11705075/22a05f48-af70-40dd-8e8c-0db21e57d7eb) ![image](https://github.com/vercel/pkg/assets/11705075/eb1d9e99-3592-4510-b990-dc123ece9f40) When run pkg command, it still look for remote base binaries. ![image](https://github.com/vercel/pkg/assets/11705075/2388f481-5599-4572-97a8-07239ab55f91)
github-actions[bot] commented 9 months 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 9 months ago

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