Skip to content
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

NodeJS in winget is not up to date #7416

Open
stefanseeger opened this issue Jan 23, 2025 · 6 comments
Open

NodeJS in winget is not up to date #7416

stefanseeger opened this issue Jan 23, 2025 · 6 comments
Labels

Comments

@stefanseeger
Copy link

URL:

https://nodejs.org/en/download/package-manager/all#windows-1

Browser Name:

Chrome

Browser Version:

128.0.6613.85

Operating System:

Windows

How to reproduce the issue:

The documentations is referencing WinGet as possiblity to install nodejs on windows.
Unfortunately, winget is only having version up to 19
https://winget.run/pkg/OpenJS/NodeJS

Can you please publish more recent version to winget

@aduh95
Copy link
Contributor

aduh95 commented Jan 23, 2025

IIUC the latest version is already there: microsoft/winget-pkgs#214140

@stefanseeger
Copy link
Author

stefanseeger commented Jan 24, 2025

Just to be more specific, I'm needing 20.18.2

stefanseeger added a commit to stefanseeger/nodejs.org that referenced this issue Jan 24, 2025
Remove winget from documentation because it is unreliable

Signed-off-by: stefanseeger <seega@gmx.com>
stefanseeger added a commit to stefanseeger/nodejs.org that referenced this issue Jan 24, 2025
other languages
@stefanseeger
Copy link
Author

With OpenJS.NodeJS.LTS I'm able to get 22.13.1
winget install --id=OpenJS.NodeJS.LTS -v "22.13.1" -e

But for version 20 LTS the expected version 20.18.2 is missing instead 20.18.0 is provided

Same for 18 LTS the expected version 18.20.6 is missing and instead 18.20.4

Maybe someone is able to dig into it

@aduh95
Copy link
Contributor

aduh95 commented Jan 24, 2025

FWIW I very agree with what you say in #7419 (comment), winget versioning is confusing. IIUC, they support only two release lines max – one per package. So OpenJS.NodeJS tracks Current releases (at the time of writing, 23.x), OpenJS.NodeJS.LTS tracks one LTS line (at the time of writing 22.x). My guess is that if you were to send a PR to add 18.20.6, it would downgrade folks who are using it to get 22.x or 23.x.

@ovflowd ovflowd added help wanted good first issue Issues for newcomers labels Feb 4, 2025
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Node.js Website Feb 4, 2025
@ovflowd ovflowd removed the bug label Feb 4, 2025
@JoshuaKGoldberg
Copy link
Contributor

Wait, is winget.run > https://winget.run/pkg/OpenJS/NodeJS the correct place to look for winget packages? It has the SEO when I Google winget node.js, but only lists v19.

https://winstall.app/apps/OpenJS.NodeJS, on the other hand, does mention 23.6.1

23.6.1 is still out of date at time of writing vs 22.13.1 🙃 but much less so.

@stefanseeger
Copy link
Author

Wait, is winget.run > https://winget.run/pkg/OpenJS/NodeJS the correct place to look for winget packages? It has the SEO when I Google winget node.js, but only lists v19.

https://winstall.app/apps/OpenJS.NodeJS, on the other hand, does mention 23.6.1

23.6.1 is still out of date at time of writing vs 22.13.1 🙃 but much less so.

You are right, this I also noticed. But forgot to mention because I was confused with the versioning generally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📋 Backlog
Development

No branches or pull requests

4 participants