-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 9 support (module 59) #2129
Comments
is this fixed by: #2130 ? |
Yes.
…On 3 Nov. 2017 8:02 am, "Stefan Penner" ***@***.***> wrote:
is this fixed by: #2130 <#2130> ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2129 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWGLHGRlWXMlh-VPUvze8OgWv_nGLks5syi3agaJpZM4QNXrU>
.
|
4.6.0 has been released with support for node 9 https://github.com/sass/node-sass/releases/tag/v4.6.0 |
How do you get Alpine working? I'm really curious |
@LaurentGoderre info is over in #1996 in the linked repo. Should add some compose files though, but I never finished them up |
Aah so it's sort of a sneaky way! a good one though |
Strange, I encounter this error when trying to
Looks quite similar to nodejs/node#13082 |
Locking this as the only outstanding issue is FreeBSD binaries. |
Yep, uploaded for 4.7.2 |
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
Preemptivly opening this issue since Node 9 was released today. We'll use this issue to track adding the support and close other issues.
Install version 4.6.0+ for Node 9 support
The text was updated successfully, but these errors were encountered: