-
Notifications
You must be signed in to change notification settings - Fork 1.3k
feat: Add Node 16 CI and drop Node 10 #3090
Conversation
Node 16 alpine image isn't out yet, so I expect this to fail for now |
This comment has been minimized.
This comment has been minimized.
@xzyfer looks like there is an internal compiler issue with some of the headers on macOS and Linux. Does this look like a Nan thing, or maybe a compiler version one. I tried bumping to GCC 8 since its' the new minimum, but I don't think it helped |
|
Experimenting with #3091 |
Looks like the OSX failure might have a fix https://github.com/microsoft/node-pty/pull/433/files |
#3091 seems to fix this, I wonder if we should be using the same compiler settings for all supported versions... |
package.json
Outdated
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "node-sass", | |||
"version": "5.0.0", | |||
"version": "5.1.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to have more research about actual compilers and C++ standards we need. Hope we do not need to use different once for different node versions?
I think one node version out, one node version in is a fair trade, we could do 6.x this way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dropped the conditionals entirely here, and the CI seems OK, but that's no guarantee 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should with the same settings as node does. Maybe they are inherited from the node gyp files, we should check this. Long time since I've had look into this...
The c++0x workaround was for the old gcc on MacOS X I think...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with bumping to 6 :)
7167506
to
7d9b9f6
Compare
- Bump to 5.1.0 - Add CI builds for 16 - Add extension lookup for module 93
- VS2015 isn't supported anymore - CPP11 flags cause issues on modern tooling
This is the minimum for Node 10 which is the oldest supported version https://github.com/nodejs/node/blob/19f3e1702e9e732462fcf83939b99d3bd0587ed2/BUILDING.md
If we have 16 builds passing I'm happy enough to move forward and deal with
any issues as they come up.
…On Sun, 2 May 2021, 5:15 am Nick Schonning, ***@***.***> wrote:
@xzyfer <https://github.com/xzyfer> @saper <https://github.com/saper> I
added the dropping on Node 10, and bumped it to 6.0.
Do you want to still work on the compiler stuff, or try the trimmed down
one and maybe add back if we get reports coming in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3090 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAENSWCKPUJS6HEPH6KHQE3TLRHLLANCNFSM43IRB52A>
.
|
Because we haven't changed the binding code I typically copy over the
binaries from the previous releases, so I'd only be rebuilding the 16
binaries for release.
…On Sun, 2 May 2021, 1:58 pm Michael Mifsud, ***@***.***> wrote:
If we have 16 builds passing I'm happy enough to move forward and deal
with any issues as they come up.
On Sun, 2 May 2021, 5:15 am Nick Schonning, ***@***.***>
wrote:
> @xzyfer <https://github.com/xzyfer> @saper <https://github.com/saper> I
> added the dropping on Node 10, and bumped it to 6.0.
> Do you want to still work on the compiler stuff, or try the trimmed down
> one and maybe add back if we get reports coming in?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#3090 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAENSWCKPUJS6HEPH6KHQE3TLRHLLANCNFSM43IRB52A>
> .
>
|
Alpine 16 seems to have some flakey CLI tests, but I think we say that in 15 for awhile too |
Feel free to land this whenever you have time to cut the release. I bumped the package.json this time 😄 |
My hero!
…On Sun, 2 May 2021, 2:03 pm Nick Schonning, ***@***.***> wrote:
Feel free to land this whenever you have time to cut the release. I bumped
the package.json this time 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3090 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAENSWAHHHZZIYDRON7CZP3TLTFH3ANCNFSM43IRB52A>
.
|
Released v6.0.0 with Node 16 support. |
Hi there. Thanks for the contributors' support on a tough issue under pressure. sass/node noobie here. Just wondering, is this problem history now? i.e. is it okay to update to node 16? From what I read above, I assume it might be okay to go to node 16 now, (although I do see 1 failed check for build 16 (I'm not sure if that affects things): https://github.com/sass/node-sass/runs/2483549702) Some days back I wrote this quick suggestion for anyone not sure what to do, but if it's now all good to go to node 16, I will update that answer to avoid node 14 and go to 16 now :) Please let mek know if my understanding is correct? |
not on mac osx its not. |
How about now? If I install the latest will it work with node 16? |
Fixes #3077
Fixes #3094