Skip to content

Conversation

@alakae
Copy link

@alakae alakae commented Jan 8, 2026

Description

This PR corrects the Devbox installation package name from node to nodejs across all localized download snippets. Currently, the download page provides instructions using devbox add node@version, but the official package name in the Nix/Devbox ecosystem is nodejs. Using node results in a package not found error.

$ devbox add node@24 
Ensuring nixpkgs registry is downloaded.
error: getting status of '/Users/XXXX/Dev/nodejs.org/nixpkgs/677fbe97984e7af3175b6c121f3c39ee5c8d62c9': No such file or directory
Ensuring nixpkgs registry is downloaded: Fail
                                                                                                                                                                                                                                                                                                   
Error: Package node@24 not found                                                                                                                                                                                                                                                                                                  

Additionally, the Turkish instructions contained two problems:

  • Typo in devbox command
  • Missing comment hashes

Validation

The change was validated by cross-referencing the official Devbox package registry on Nixhub, which confirms that nodejs is the correct identifier for the runtime.

See: https://www.nixhub.io/packages/nodejs vs https://www.nixhub.io/packages/node

Related Issues

No related issue. This is a direct fix for incorrect installation instructions found on the /en/download page.

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@alakae alakae requested a review from a team as a code owner January 8, 2026 12:54
@vercel
Copy link

vercel bot commented Jan 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
nodejs-org Ready Ready Preview Jan 8, 2026 2:14pm

@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website

Please review the changes when you have a chance. Thank you! 🙏

@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

Note

Your Pull Request seems to be updating Translations of the Node.js Website.

Whilst we appreciate your intent; Any Translation update should be done through our Crowdin Project.
We recommend giving a read on our Translation Guidelines.

Thank you!

Copy link
Member

@avivkeller avivkeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please only change the English variation

@ovflowd
Copy link
Member

ovflowd commented Jan 8, 2026

Didn't we remove DevBox because it was a commercial product?

@alakae
Copy link
Author

alakae commented Jan 8, 2026

Please only change the English variation

I have changed this as requested; obviously the fixes for the Turkish version have now disappeared as well

@avivkeller
Copy link
Member

avivkeller commented Jan 8, 2026

Didn't we remove DevBox because it was a commercial product?

No. DevBox is still on the website. Although, per https://openjs-foundation.slack.com/archives/CVAMEJ4UV/p1744674880071739, I think it should be removed.

@ovflowd
Copy link
Member

ovflowd commented Jan 8, 2026

Didn't we remove DevBox because it was a commercial product?

No. DevBox is still on the website. Although, per openjs-foundation.slack.com/archives/CVAMEJ4UV/p1744674880071739, I think it should be removed.

Then we should close this PR and make a new one to remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants