-
Notifications
You must be signed in to change notification settings - Fork 65
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Node.js 11.1.0 #2707
Comments
@FeodorFitsner any ETA for this? The milestone's deadline has passed and it seems like node 11 is still unavailable 😞 |
Node 11 appears to have been available for about week. We are using it in
the node-sass project.
…On Fri., 9 Nov. 2018, 9:29 am Antón Molleda ***@***.*** wrote:
@FeodorFitsner <https://github.com/FeodorFitsner> any ETA for this? The
milestone's deadline has passed and it seems like node 11 is still
unavailable 😞
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2707 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWFIqvBQMbc5O40rbi6wOUUmfFG6oks5utLBZgaJpZM4X3EIm>
.
|
🤔this issue is from 4 days ago: nstepien/iltorb#79 |
Image distribution is in progress right now, We believe it should be available in the couple of days. |
Actually you can switch to 11.1 already, the way it described here: https://www.appveyor.com/docs/lang/nodejs-iojs/ With new image switch will be faster, but again you already can use it. |
@IlyaFinkelshteyn I tried for a while to get |
@chearon please run the following command in PowerShell at some build stage (say
|
Yes The documentation implies |
No description provided.
The text was updated successfully, but these errors were encountered: