Node.js and pnpm

Using an installed release

Elmony includes Node.js 24.19.0 and pnpm 10.20.0. You do not need a system installation of Node.js, npm, Corepack, or pnpm, and you should not point Elmony at C:\Program Files\nodejs during normal use.

• Managed runtime missing or invalid: Close Elmony and reinstall the latest official package for your operating system and CPU architecture. Startup validates both bundled versions before opening the app.
• Dependency installation is slow: The runtime is bundled, but each project may still download packages from its configured registry. Check your network, proxy, VPN, and registry availability.
• A preview will not start: Open the Console in the Builder for the actual install or server error. Use Restart first; use Rebuild from the preview menu if dependencies need to be installed again.

Development and unpackaged builds

A source checkout or unpackaged development build falls back to tools on your system. In that case, confirm they are available in a new terminal:

node --version
pnpm --version

Install a supported Node.js LTS release if node is missing. To match the packaged runtime, install pnpm 10.20.0:

npm install -g pnpm@10.20.0

If Node.js works in the terminal but is not detected, restart Elmony so it inherits the updated PATH. Development builds can also use the Node.js path picker in Settings.

Still stuck?

Open Help → Report a bug inside Elmony and include the startup or Console error. Mention whether you are using an installed release or running from source.