AlmaLinux 9 DNF Module Streams: Decision Guide and nodejs:18 Implementation

The decision: default packages, module streams, or third‑party repos

\n

You need Node.js 18 on AlmaLinux 9, but the default AppStream package ships Node.js 12. You have three realistic options: accept the default version, enable a DNF module stream, or add a third‑party repository such as nodesource. This guide helps you pick, then shows a concrete implementation and validation for the stream option.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Option	Support & updates	Version flexibility	Risk
Default AppStream packages	Full AlmaLinux security updates for the OS lifecycle	None — one version per name	Lowest
DNF module streams	Updated alongside the base OS from official mirrors	Several curated streams per application	Moderate — stream switches can break dependencies
Third‑party repos	Vendor‑dependent; no AlmaLinux guarantee	Widest (latest upstream releases)	Higher — metadata conflicts, supply‑chain risk

\n

Constraints to understand before enabling a stream

\n

\n
• One stream per name, system‑wide. Enabling nodejs:18 replaces what nodejs resolves to for every package and dependency on the host. You cannot run nodejs:16 and nodejs:18 side by side via modules (use containers for that).
\n
• Switching streams is not a clean upgrade. Changing from one enabled stream to another after packages are installed can leave mismatched dependencies. Reset first (dnf module reset nodejs) or, ideally, pick the stream on a fresh system.
\n
• Third‑party repos may lack modular metadata. Mixing them with streams can cause dependency resolution failures. Disable conflicting repos before enabling a stream.
\n
• Streams have their own lifecycles. A stream can reach end‑of‑life before the OS does; check the stream’s support window before standardizing on it.
\n

\n

Implementation: enabling nodejs:18

\n

Run the following commands as root (or via sudo) on the AlmaLinux 9 host.

\n

dnf module list nodejs

\n

You should see entries like nodejs 18 [e] or nodejs 20 with a hint column marking the default ([d]).

\n

Enable and install the 18 stream:

\n

dnf module enable nodejs:18 -y\ndnf module install nodejs:18 -y

\n

On a fresh system you can combine these into dnf module install nodejs:18, which enables the stream implicitly. If a different stream was previously enabled, reset first:

\n

dnf module reset nodejs -y\ndnf module install nodejs:18 -y

\n

Be aware that resetting and reinstalling may remove dependent packages; review the transaction summary DNF prints before confirming.

\n

Validation

\n

\n
1. Stream state: dnf module list --enabled should show nodejs 18 [e].
\n
2. Installed version: node --version should report v18.x. If it reports another major version, a conflicting repo likely supplied the package — check dnf info nodejs for the From repo field.
\n
3. Update path: dnf update --refresh should offer only nodejs 18.x updates, not a jump to another major version.
\n

\n

Limitations

\n

Exact stream availability varies by AlmaLinux 9 minor release and mirror sync state, so verify with dnf module list on your own system rather than assuming a stream exists. Streams also do not help with software AlmaLinux does not package at all. For per‑project version isolation, containers (Podman is included) are a better fit than modules.