Skip to content
This repository has been archived by the owner on Jan 13, 2024. It is now read-only.

Abbility to use other version than v7,v8,etc #171

Closed
mkg20001 opened this issue Jul 22, 2017 · 6 comments
Closed

Abbility to use other version than v7,v8,etc #171

mkg20001 opened this issue Jul 22, 2017 · 6 comments

Comments

@mkg20001
Copy link

Currently I haven't found a way to use a version like v8.2.1
Is that possible?

@nmchau
Copy link

nmchau commented Jul 23, 2017

I have the same problem....
According to the document, if we don't specify the target node version, then the latest version will be applied... So the version should have been v8.2.1 in this case instead of v8.0.0?

@dizlexik
Copy link

I'm definitely interested in this too.

I posted a similar question to Slack a few days ago but didn't get an answer:
https://zeit-community.slack.com/messages/C57C53R6K/p1500653904026892

Is it true that pkg can only produce binaries with Node versions that exist here?
https://github.com/zeit/pkg-fetch/blob/master/patches/patches.json

If I wanted to target Node 8.2.1 I would not be able to do that until a patch exists for it, correct?

@igorklopov
Copy link
Contributor

@dizlexik Please wait for new pkg release

xdevs23 pushed a commit to xdevs23/pkg that referenced this issue Jul 26, 2017
@igorklopov
Copy link
Contributor

Please try pkg@4.1.4 and pass something like -t node8.2.1 to pkg command line.

@dizlexik
Copy link

Thanks, that's great.

But just to clarify, as I understand it any new Node version that comes out will require some amount of work from you to create a corresponding patch before it can be used with pkg. So there will always be some lag time between Node release and pkg support, even in the case of an important security patch. Is there any guarantee on the timeframe between Node release and pkg supporting it or does it depend more on when you have the free time to work on it?

Also I would love to use this in production so I'm wondering what the plan is regarding ongoing releases. Is there a plan in place to make sure this project lives on for the years to come, or is there a chance that releases may stop suddenly without warning at some point? It's a Zeit project so I'm inclined to think you guys have thought this all through since you're awesome like that, but I just wanted to make sure and was wondering if this is documented anywhere. Thanks!

@igorklopov
Copy link
Contributor

There is upcoming solution to use original node binary instead of patched one. Stay tuned!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants