Rocky Linux 10 bundles Node.js 22 in AppStream, which covers most use cases. But if you need npm 11’s faster dependency resolution, V8 13.6 for Float16Array support, or the promoted permission model, Node.js 24 Krypton is the current Active LTS and the right move.<\/p>\n\n\n\n
This guide walks through three ways to install Node.js 24 on Rocky Linux 10, AlmaLinux 10, and RHEL 10, with real command output from a test VM. After installation, we build a working Express.js API, run the built-in test runner, configure a systemd service<\/a> for production, and cover SELinux and firewalld configuration. If you run Ubuntu or Debian, see the Ubuntu 24.04\/22.04 guide<\/a> or the Debian 13\/12 guide<\/a> instead.<\/p>\n\n\n\n Before installing, check whether Node.js is already on the system:<\/p>\n\n\n\n Rocky Linux 10 ships Node.js 22 in the AppStream repository as a module stream. That version works fine for many projects, but it does not include Node.js 24. The methods below get you the latest LTS release.<\/p>\n\n\n\n Three methods are available. Pick one based on your use case: NodeSource for production servers with automatic dnf updates, NVM for development machines that need multiple Node.js versions<\/a>, or the binary tarball for air-gapped or custom setups.<\/p>\n\n\n\n NodeSource tracks upstream Node.js releases and packages them as RPMs that integrate with dnf. Updates arrive within hours of each Node.js release.<\/p>\n\n\n\n If the AppStream Add the NodeSource repository for Node.js 24:<\/p>\n\n\n\n Install Node.js (npm and npx are bundled):<\/p>\n\n\n\n Verify the installation:<\/p>\n\n\n\n Confirmed output from a Rocky Linux 10 VM:<\/p>\n\n\n\n Check the V8 engine version and platform:<\/p>\n\n\n\n V8 13.6 confirmed on the test VM:<\/p>\n\n\n\n NVM installs Node.js in your home directory and lets you switch between multiple Node.js versions<\/a> per project. No sudo required for npm global installs.<\/p>\n\n\n\n Install NVM (auto-detects the latest release from GitHub):<\/p>\n\n\n\n Reload your shell:<\/p>\n\n\n\n Install Node.js 24 and set it as the default:<\/p>\n\n\n\n Switch between versions any time with Download the prebuilt binary directly from nodejs.org. This works on any Linux system regardless of package manager. The version auto-detects from the Node.js download API:<\/p>\n\n\n\n Verify:<\/p>\n\n\n\n Packages like NVM users get this handled automatically when Node.js compiles from source, but NodeSource and tarball installs need it explicitly.<\/p>\n\n\n\n Rocky Linux 10 runs SELinux in enforcing mode. Node.js works with the default policy when running on standard ports. No custom booleans or context changes are needed for a typical Node.js application.<\/p>\n\n\n\n Verify there are no SELinux denials after starting your Node.js application:<\/p>\n\n\n\n If the output shows no matches, SELinux is not blocking anything. If you bind Node.js to a non-standard port (anything other than common HTTP ports), you may need to allow it:<\/p>\n\n\n\n Rocky Linux 10 uses firewalld by default. Open port 3000 for your Node.js application:<\/p>\n\n\n\n Verify the port is open:<\/p>\n\n\n\n You should see A quick demo confirms the full stack works. Initialize a project and install Express:<\/p>\n\n\n\n Create the server file:<\/p>\n\n\n\n Add the following Express application:<\/p>\n\n\n\n Start the server:<\/p>\n\n\n\n From another terminal, hit the API:<\/p>\n\n\n\n Real JSON response from our Rocky Linux 10 test VM:<\/p>\n\n\n\n Node.js 24 ships a production-ready test runner in the Create a test file:<\/p>\n\n\n\n Add the following test cases:<\/p>\n\n\n\n Run the tests:<\/p>\n\n\n\n Real output from our Rocky Linux 10 VM:<\/p>\n\n\n\n For production deployments, configure systemd<\/a> to start your Node.js app on boot and restart it on crashes.<\/p>\n\n\n\n Create a dedicated user for the application:<\/p>\n\n\n\n Create the service unit file:<\/p>\n\n\n\n Add the following configuration:<\/p>\n\n\n\n Enable and start the service:<\/p>\n\n\n\n Check the service status:<\/p>\n\n\n\n The service should show active (running). View application logs with:<\/p>\n\n\n\n For more advanced process management with cluster mode, log rotation, and zero-downtime reloads, look at PM2 process manager<\/a>.<\/p>\n\n\n\n If you are running Node.js 22 from the AppStream module or an older NodeSource repository, here is how to upgrade to Node.js 24.<\/p>\n\n\n\n Remove the existing Node.js installation and disable the AppStream module if active:<\/p>\n\n\n\n Add the NodeSource 24.x repository and install:<\/p>\n\n\n\n Verify the upgrade:<\/p>\n\n\n\n After upgrading, rebuild any native modules in your projects:<\/p>\n\n\n\n The NODE_MODULE_VERSION changed from 134 (Node.js 22) to 137 (Node.js 24), so native addons compiled for Node.js 22 will not work without a rebuild.<\/p>\n\n\n\n If your project is stable on Node.js 22 and you don’t need the new features, staying on 22 through April 2027 is fine. Upgrade when you need npm 11, the V8 13.6 improvements, or when Node.js 22 enters end-of-life.<\/p>\n\n\n\n Some projects require Yarn. Install Yarn Classic globally:<\/p>\n\n\n\n For Yarn 4.x (Berry), enable Corepack inside your project:<\/p>\n\n\n\n To completely remove Node.js installed via NodeSource:<\/p>\n\n\n\n For NVM installations, remove the version and optionally NVM itself:<\/p>\n\n\n\nWhat You Need<\/h2>\n\n\n\n
\n
Check Your Current Node.js Version<\/h2>\n\n\n\n
node -v 2>\/dev\/null || echo \"Node.js not installed\"\nnpm -v 2>\/dev\/null || echo \"npm not installed\"<\/code><\/pre>\n\n\n\nInstall Node.js 24 on Rocky Linux 10<\/h2>\n\n\n\n
Method 1: NodeSource Repository (Recommended for Production)<\/h3>\n\n\n\n
nodejs<\/code> module is enabled, disable it first so it does not conflict with NodeSource:<\/p>\n\n\n\nsudo dnf module disable -y nodejs<\/code><\/pre>\n\n\n\ncurl -fsSL https:\/\/rpm.nodesource.com\/setup_24.x | sudo bash -<\/code><\/pre>\n\n\n\nsudo dnf install -y nodejs<\/code><\/pre>\n\n\n\nnode -v\nnpm -v<\/code><\/pre>\n\n\n\nv24.14.0\n11.9.0<\/code><\/pre>\n\n\n\nnode -e \"console.log('Platform:', process.platform, process.arch); console.log('V8:', process.versions.v8)\"<\/code><\/pre>\n\n\n\nPlatform: linux x64\nV8: 13.6.233.17-node.41<\/code><\/pre>\n\n\n\nMethod 2: NVM (Best for Development)<\/h3>\n\n\n\n
NVM_VER=$(curl -s https:\/\/api.github.com\/repos\/nvm-sh\/nvm\/releases\/latest | grep tag_name | cut -d \\\" -f4)\ncurl -o- https:\/\/raw.githubusercontent.com\/nvm-sh\/nvm\/${NVM_VER}\/install.sh | bash<\/code><\/pre>\n\n\n\nsource ~\/.bashrc<\/code><\/pre>\n\n\n\nnvm install 24\nnvm alias default 24\nnode -v<\/code><\/pre>\n\n\n\nnvm use 22<\/code> or nvm use 24<\/code>. For production servers, NodeSource is still the better choice because NVM does not provide automatic security updates through dnf.<\/p>\n\n\n\nMethod 3: Official Binary Tarball<\/h3>\n\n\n\n
NODE_VER=$(curl -s https:\/\/nodejs.org\/dist\/latest-v24.x\/ | grep -oP 'node-v\\K[0-9.]+' | head -1)\ncurl -sLO https:\/\/nodejs.org\/dist\/v${NODE_VER}\/node-v${NODE_VER}-linux-x64.tar.xz\nsudo tar xJf node-v${NODE_VER}-linux-x64.tar.xz -C \/usr\/local --strip-components=1\nrm node-v${NODE_VER}-linux-x64.tar.xz<\/code><\/pre>\n\n\n\nnode -v\nnpm -v<\/code><\/pre>\n\n\n\nInstall Build Tools for Native Modules<\/h2>\n\n\n\n
bcrypt<\/code>, sharp<\/code>, and sqlite3<\/code> compile native C\/C++ addons during npm install<\/code>. Without the build toolchain, they fail with gyp ERR!<\/code> errors:<\/p>\n\n\n\nsudo dnf install -y gcc-c++ make<\/code><\/pre>\n\n\n\nSELinux Configuration<\/h2>\n\n\n\n
sudo ausearch -m avc -ts recent<\/code><\/pre>\n\n\n\nsudo semanage port -a -t http_port_t -p tcp 3000<\/code><\/pre>\n\n\n\nConfigure Firewalld<\/h2>\n\n\n\n
sudo firewall-cmd --permanent --add-port=3000\/tcp\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\nsudo firewall-cmd --list-ports<\/code><\/pre>\n\n\n\n3000\/tcp<\/code> in the output. For production deployments behind Nginx or Apache, open port 443\/tcp instead and proxy traffic to the Node.js backend.<\/p>\n\n\n\nBuild an Express.js API (Demo Project)<\/h2>\n\n\n\n
mkdir -p ~\/node-demo && cd ~\/node-demo\nnpm init -y\nnpm install express<\/code><\/pre>\n\n\n\nvi ~\/node-demo\/server.js<\/code><\/pre>\n\n\n\nconst express = require(\"express\");\nconst app = express();\nconst PORT = 3000;\n\napp.get(\"\/\", (req, res) => {\n res.json({\n message: \"Node.js 24 LTS running on Rocky Linux 10\",\n nodeVersion: process.version,\n v8Version: process.versions.v8,\n platform: process.platform,\n arch: process.arch,\n uptime: process.uptime()\n });\n});\n\napp.listen(PORT, () => console.log(\"Server running on port \" + PORT));<\/code><\/pre>\n\n\n\nnode ~\/node-demo\/server.js<\/code><\/pre>\n\n\n\ncurl http:\/\/localhost:3000\/<\/code><\/pre>\n\n\n\n{\n \"message\": \"Node.js 24 LTS running on Rocky Linux 10\",\n \"nodeVersion\": \"v24.14.0\",\n \"v8Version\": \"13.6.233.17-node.41\",\n \"platform\": \"linux\",\n \"arch\": \"x64\",\n \"uptime\": 2.008696158\n}<\/code><\/pre>\n\n\n\nUse the Built-in Test Runner<\/h2>\n\n\n\n
node:test<\/code> module. For projects that don’t need Jest’s mocking framework or Mocha’s plugin ecosystem, it covers the basics without any npm dependencies.<\/p>\n\n\n\nvi ~\/node-demo\/test.mjs<\/code><\/pre>\n\n\n\nimport { test } from \"node:test\";\nimport assert from \"node:assert\";\n\ntest(\"math works\", () => {\n assert.strictEqual(1 + 1, 2);\n});\n\ntest(\"node version is 24\", () => {\n assert.ok(process.version.startsWith(\"v24\"));\n});<\/code><\/pre>\n\n\n\nnode --test ~\/node-demo\/test.mjs<\/code><\/pre>\n\n\n\n\u2714 math works (0.481963ms)\n\u2714 node version is 24 (0.126785ms)\n\u2139 tests 2\n\u2139 suites 0\n\u2139 pass 2\n\u2139 fail 0\n\u2139 cancelled 0\n\u2139 skipped 0\n\u2139 todo 0\n\u2139 duration_ms 39.468755<\/code><\/pre>\n\n\n\nRun Node.js as a systemd Service<\/h2>\n\n\n\n
sudo useradd -r -s \/sbin\/nologin nodeapp<\/code><\/pre>\n\n\n\nsudo vi \/etc\/systemd\/system\/nodeapp.service<\/code><\/pre>\n\n\n\n[Unit]\nDescription=Node.js Application\nAfter=network.target\n\n[Service]\nType=simple\nUser=nodeapp\nWorkingDirectory=\/opt\/myapp\nExecStart=\/usr\/bin\/node server.js\nRestart=on-failure\nRestartSec=5\nEnvironment=NODE_ENV=production\nStandardOutput=journal\nStandardError=journal\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n\n\n\nsudo systemctl daemon-reload\nsudo systemctl enable --now nodeapp<\/code><\/pre>\n\n\n\nsudo systemctl status nodeapp<\/code><\/pre>\n\n\n\nsudo journalctl -u nodeapp -f<\/code><\/pre>\n\n\n\nUpgrade from Node.js 22 to Node.js 24<\/h2>\n\n\n\n
sudo dnf remove -y nodejs\nsudo dnf module disable -y nodejs<\/code><\/pre>\n\n\n\ncurl -fsSL https:\/\/rpm.nodesource.com\/setup_24.x | sudo bash -\nsudo dnf install -y nodejs<\/code><\/pre>\n\n\n\nnode -v\nnpm -v<\/code><\/pre>\n\n\n\ncd \/path\/to\/your\/project\nnpm rebuild<\/code><\/pre>\n\n\n\nNode.js 22 vs Node.js 24<\/h2>\n\n\n\n
Component<\/th> Node.js 22 (Jod)<\/th> Node.js 24 (Krypton)<\/th><\/tr><\/thead> Status<\/td> Maintenance LTS (until Apr 2027)<\/td> Active LTS (until Apr 2028)<\/td><\/tr> V8 Engine<\/td> 12.4<\/td> 13.6<\/td><\/tr> npm<\/td> 10.x<\/td> 11.9<\/td><\/tr> Test runner<\/td> Stable (basic)<\/td> Stable (global setup\/teardown, auto subtest)<\/td><\/tr> Permission model<\/td> --experimental-permission<\/code><\/td>--permission<\/code> (promoted)<\/td><\/tr>using<\/code> keyword<\/td>Not available<\/td> Explicit resource management<\/td><\/tr> URLPattern<\/td> Requires import<\/td> Global (no import needed)<\/td><\/tr> SQLite<\/td> Experimental<\/td> Stable with transactions, aggregates<\/td><\/tr> NODE_MODULE_VERSION<\/td> 134<\/td> 137<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Install Yarn<\/h2>\n\n\n\n
sudo npm install -g yarn\nyarn --version<\/code><\/pre>\n\n\n\ncorepack enable\nyarn set version stable<\/code><\/pre>\n\n\n\nUninstall Node.js<\/h2>\n\n\n\n
sudo dnf remove -y nodejs\nsudo rm -f \/etc\/yum.repos.d\/nodesource*.repo\nsudo dnf clean all<\/code><\/pre>\n\n\n\nnvm uninstall 24\nrm -rf ~\/.nvm<\/code><\/pre>\n\n\n\nKey Features in Node.js 24<\/h2>\n\n\n\n