Node 18 support (module 108)

[nschonni]

Support should land on April 19, 2022.

• Add 18 to CI
• Add the Module version to extensions.js
• Update support table in README.md
• Choose if this should be a v8 or v7.1 for the version
• Update Windows builds to Windows 2019 Windows 2016 runners being removed in March 2022 #3212

Related but different timing:

• Node 12 EOL is on the 23rd Drop support for Node 12 #3250
• Node 17 EOL is June 1st 2020 Drop support for Node 17 #3252

[the-hotmann]

Support should land on April 19, 2022.

Are there any news on this? I tested it with Node18 and yes, with the lower versions (18.1 I guess) it worked, but with 18.7 and 18.6 it does not work. I would love to see this running on Node18 :)

Thanks!

[eduardocque]

any news about support to node 18 ?

[eduardocque]

@nschonni @xzyfer hi i would like to ask if you have an expected day to release this please

Regards

[MikeMcC399]

Node.js 18 moved to Active LTS status on Oct 25, 2022. See https://github.com/nodejs/release#release-schedule and https://nodejs.org/en/blog/release/v18.12.0/

[preichelt]

@nschonni any updates on Node 18 support now that 18 is Active LTS?

[pangyongsheng]

when will it be finshed

[pangyongsheng]

when will it be finshed

[preichelt]

I can at least confirm that we're successfully running node-sass 7.0.3 with Node 18.12.0 without any issues so far.

[MarcoKramer]

I can at least confirm that we're successfully running node-sass 7.0.3 with Node 18.12.0 without any issues so far.

I can confirm the same. It did require installing make and g++ to get it working.

[Nic128]

No it does not.

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (108)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v7.0.3
    at module.exports .....
    .....

We need this PR. #3257

[MikeMcC399]

@nschonni

You wrote in this issue:

Node 17 EOL is June 1st 2020

That should be 2022, as you wrote in #3252.

In any case it is a date in the past! Maybe you'd like to correct this in the above original post?