-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Node.js 10.x #6
Comments
Hi Anand, I bumped to Node 12 because I used What prevents you from using only the latest LTS version of Node? I'm aware v10 hasn't technically reached EOL yet so if you need it I'll add it back. However I'm currently on a tight deadline schedule @ work so it'd be helpful if you told me how critical that is for you. Otherwise I might have to delay this by ~2 weeks. |
Thanks for the swift reply! My project @staart/api is dependent on If you like, I can open a PR replacing |
@GitSquared Thanks for the lib and for the prompt reply. Node 10 has just transitioned to maintenance LTS. However you will see in the following chart that it's is still prominent. It will be relevant to the broader user base.
|
I'm well aware of the usage share of v10, thank you. People still use windows XP too, doesn't mean I have to support it. |
Happy to wait. Thanks for your hard work! Stay safe! |
You too.
…On Apr 2 2020, at 10:49 am, Anand Chowdhary ***@***.***> wrote:
Happy to wait. Thanks for your hard work! Stay safe!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#6 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AF24SIN7R7MQIYAB6LVELSLRKRGQZANCNFSM4LZUV5IA).
|
@AnandChowdhary Thanks for your patience. |
Hey @GitSquared, thanks for all your hard work with this package!
Is there a specific Node.js 12.x feature that's important for this, and is there any way we can support Node.js 10.x?
Issue context: staart/api#1071
The text was updated successfully, but these errors were encountered: