-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Broken link on Downloading Node.js #7589
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
Comments
FWIW - it works on my machine (Windows, Chrome), so curious to learn more what is at fault here |
According to https://nodejs.org/en/blog/release/v22.14.0 there is no file The nearest would be Linux 64-bit Binary: https://nodejs.org/dist/v22.14.0/node-v22.14.0-linux-x64.tar.xz |
That file is not in the expected files for v22 (see https://github.com/nodejs/build/blob/main/ansible/www-standalone/tools/promote/expected_assets/v22.x). |
I really can't reproduce this issue on Chrome for Android. |
Maybe we should tag @nodejs/releasers @nodejs/release here as this isn't really a website issue, at best a Cloudflare Worker, but feels like something even deeper. |
No it's definitely a website issue if the website links to a release asset that doesn't exist, seems that Jean's mobile browser found some edge-case. |
You mean a website issue on the blog post? Or on the cloudflare worker or where exactly? Im still trying to understand what supposedly is wrong here 🤔 |
There's a wrong assumption in nodejs.org/apps/site/util/getUserPlatform.ts Lines 6 to 15 in 1ef006f
nodejs.org/apps/site/util/getNodeDownloadUrl.ts Lines 53 to 58 in 7efa770
|
This issue seems to be happening when looking the website with Androind and Chrome - I did not check with other browser yet
Issue: when clicking on the download button on the nodejs.org website, when using the previous stated config you are redirected to a page crashing as the link does not seems to exist
Impacted link: https://nodejs.org/dist/v22.14.0/node-v22.14.0-linux-x86.tar.xz
I will submit a PR to fix it :)
The text was updated successfully, but these errors were encountered: