Add link to WSL2 install to download page

[mattwojo]

• Node.js Version: ALL
• OS: Windows
• Scope: Install

Windows is recommending that Node.js be installed on WSL2 (the subsystem for Linux, running the latest version of Ubuntu) for an optimal experience doing Node.js development.

At the bottom of the Node.js download page there is a list of links:

Signed SHASUMS for release files (How to verify) All download options Installing Node.js via package manager Previous Releases Nightly builds Node-ChakraCore Nightly builds Building Node.js from source on supported platforms Installing Node.js via binary archive on Linux

Similar to this request, it would be helpful if this list of links included a link to the instructions to install on WSL2 (now the recommendation from Windows). Maybe something like this:

Signed SHASUMS for release files (How to verify) All download options Installing Node.js via package manager Installing Node.js via the Windows subsystem for Linux (WSL2) Previous Releases Nightly builds Node-ChakraCore Nightly builds Unoffical builds Building Node.js from source on supported platforms Installing Node.js via binary archive on Linux

This is a MUCH more happy path for anyone using Node.js on Windows!

Thanks!!

[nschonni]

now the recommendation from Windows

Where are you seeing this?

[mattwojo]

https://docs.microsoft.com/windows/nodejs/ Instructions > https://docs.microsoft.com/en-us/windows/nodejs/setup-on-wsl2 Recommendation from the Beginners page > https://docs.microsoft.com/en-us/windows/nodejs/beginners

[nschonni]

OK, i've opened an issue over there, since suggesting that beginners change to the "Insiders" ring of Windows and install WSL2 that isn't finalized doesn't seem like great advice IMO.

[mattwojo]

Thanks @nschonni. Try it -- it will change your mind. : ) Do you have a link to the issue you opened?

*As a bit of background, the company is committed, the way Windows works, it just isn't possible to release changes like this at any time... they need to be tied to a Windows release... thus we're stuck waiting and keeping folks on the "Insiders" ring until then. Guessing that will be some time mid-next year..?

[Trott]

@nodejs/platform-windows

[RReverser]

The recommendation sounds strange to me, to be honest. Node.js working great across various platforms, including Windows, has always been one of its main strengths, and we haven't had any Windows-specific issues for quite a long time (not counting some outdated native packages or Linux-specific build commands, which are not fixed by this but rather the opposite).

I don't have anything against adding WSL as another option to the list, but I certainly wouldn't consider it the easiest path for beginners nor would recommend it as the "right path" to start with.

If anything, this makes it even harder to ensure portability, because folks authoring and testing scripts exclusively on WSL often will expect them to run on any Windows machine and will be surprised when they don't.

Finally, as mentioned above, WSL2 is currently available only as part of the experimental Insiders builds, and while there are many who happily participate in this program for faster feedback (me included), running potentially unstable builds is not an option for majority of users or developers.

[mattwojo]

Thanks @RReverser. I'll connect with the stakeholders and suggest re-thinking the recommendation to start beginners out on WSL. For this specific request, I'm really just asking to list the WSL2 install as an option for folks to try if they feel comfortable using the Insiders build... the popularity and response to using Node.js with WSL2 tells me that folks would be interested, so I'm just looking to surface the how-to instructions given the initial setup is a bit complex. The links section of the Node.js downloads page seemed to be a logical place for this.

[richardlau]

Alternatively it could be added to https://nodejs.org/en/download/package-manager/ which already lists nvm and currently lists some package managers for Windows (e.g. Chocolatey).

[mattwojo]

I'm good with whatever you all think is best. I did file a PR here: https://github.com/nodejs/nodejs.org/pull/2692

Though I'm not sure that I did it correctly and can close and file another on the /package-manager page if that seems like the better option.