Node.js Settings
Change the Eenos server default Node.js runtime and understand system Node/npm link and Yarn setup effects.
Open Runtimes → Node.js → Node.js Settings.
Runtime list
The table shows runtime name, vendor, version, default/available status and action. It is populated from the configured installed runtime inventory. Available is not a running-application health check.
Search, sort or paginate to locate a version. The default page size is 25, with 10, 50, 100 and All available.
Set a default
- Record the current server default and dependent applications/scripts.
- Find the intended installed version.
- Click Set as default.
- Review the runtime in the confirmation.
- Click Set as Default, or Cancel.
- Read the result and verify the saved default and command-line behavior.
The request contains a required runtime selection with a maximum length of 20 characters. The helper checks the installed version inventory and requires both the selected Node and npm executable before changing it.
What changes
The helper saves the default and replaces the system Node/npm links in the standard system and local command directories with links to the selected runtime. If the system Yarn executable is absent, it invokes Yarn setup.
System command consumers are affected
Scripts, cron jobs, build tools and interactive commands using system Node/npm can use the new default. This is broader than changing one domain. Review those consumers and preserve the previous selection before confirming.
This helper does not invoke an all-domain virtual-host rebuild or explicitly restart application processes. Domains configured with an explicit version retain their saved selection. Verify inherited domains through their effective configuration and running application.
Failures and verification
A missing runtime or executable is rejected. Link or setup failures can occur after the preference has been written, so inspect the saved default and actual command links before retrying.
Confirm the application's required packages and native modules work with the selected runtime. A panel success message does not prove package compatibility or that existing processes have restarted.
Demo sessions cannot change the default. If the runtime inventory is missing, resolve installation/configuration through the appropriate administrator workflow rather than submitting a version string that is not offered.