-
Notifications
You must be signed in to change notification settings - Fork 199
Specify a custom node binary with PKG_NODE_PATH #43
Conversation
@igorklopov Can you have a look regarding this new feature? It will be very useful! Thank you. |
Can we document the flag in README? |
Closing as inactive, feel free to open a new PR and we can get this through 🙏 |
@leerob with this only being a 2 line change is there any reason not to allow this? |
@OmgImAlexis there hadn't been any activity in years here. Is there an open issue related to this - or how did you find this? Happy to reconsider if multiple people are interested. |
I've been subscribed for about a year. There's no activity as you'll find most long terms GitHub users won't comment as they're met with the "don't +1 this" instead we just subscribe. I assumed the PR was good to go and just hadn't been merged. My issue was wanting to pass in a custom version for development as someone else stated. |
@OmgImAlexis Ahh, got it! In that case, happen to re-open. |
For more clarity, this needs:
And then I will +1 and merge/release! |
Docs should be added on pkg readme, in this section: https://github.com/vercel/pkg#environment |
is anyone still interested in this? |
For anyone that is enterested in this project, giving that I don't receive any feedback from Vercel anymore, I created my own forks of both pkg and pkg-fetch: If someone is interested in helping me create a PR or move your active PR to those repositories. Thanks 🙏🏼 |
This has been added by: yao-pkg#7 |
(This is useful for packaging a debug build of node.)