---
title: "Node.js configuration"
url: https://docs.corefinity.com/guides/sites/software-and-services/node-js
type: guide
last_updated: 2026-11-13
feature: node-runtime
related:
  - https://docs.corefinity.com/api/reference/runtime/get-node-catalogue.md
  - https://docs.corefinity.com/api/reference/runtime/get-node-package.md
  - https://docs.corefinity.com/api/reference/runtime/get-node-runtime.md
  - https://docs.corefinity.com/api/reference/runtime/update-node-runtime.md
  - https://docs.corefinity.com/api/reference/runtime/copy-node-runtime.md
  - https://docs.corefinity.com/api/reference/runtime/clear-node-caches.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_runtime_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_catalogue_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_version_change.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_packages_update.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_package_lookup.md
  - https://docs.corefinity.com/mcp/tools/corestack_node_packages_check.md
---
# Node.js configuration

Choose the Node.js version a site builds with, add global packages and follow the version your repository asks for.

## Before you start

- You can open the site in **Managed Websites**. Anyone who can open a site can change its Node.js configuration.
- Each environment has its own version and packages: choose **Production** or **Staging** in the site header first.

## Change the version

1. **Open the version list**

   Go to **Managed Websites**, choose the site, then **Software & services** under **Site settings**. Choose **Change…** beside **Node.js**.

   _Screenshot: The Services card of a site. The Node.js row shows version 24, Maintenance LTS, with the buttons Change… and Configure…._

2. **Choose the version**

   Choose a version under **Recommended** or **Supported**. The dialog lists what else changes, then the button names your choice, such as **Change to Node.js 26**.

   _Screenshot: The Change Node.js version dialog with 26, Active LTS, chosen above 24 and 22. A note says projects with native modules need npm rebuild, and the button reads Change to Node.js 26._

3. **Review and apply**

   Choose **Review and apply**, then **Apply**.

   _Screenshot: Node.js configuration with the version change waiting. The bar at the bottom counts one change beside Discard and Review and apply._

Your first change on an environment also turns on instant changes, now or in tonight's maintenance window as the card says.

After that, a change applies straight away. Commands that are running keep their version; new ones use the version you chose.

An end-of-life version asks you to tick a box saying it gets no security fixes.

## Add a global package

1. **Open Node.js configuration**

   Choose **Configure…** beside **Node.js**, then **Add package**.

2. **Choose the package**

   Choose one of the **Common tools** or enter a package name from npm. Leave **Version** empty for the newest, or enter the one you need, then choose **Add**.

   _Screenshot: Node.js configuration with Add package open. Common tools lists gulp-cli, grunt-cli, typescript and others, above a Version field reading newest and the note Public npm registry only, up to 20 packages. The installed packages are listed underneath._

3. **Review and apply**

   Choose **Review and apply**, then **Apply**.

An environment keeps up to 20 global packages, from the public npm registry only. yarn and pnpm are built in through Corepack.

## Settings

| Setting                   | What it does                                                                                                                                                                                  |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Follow the repository** | Before each deployment, switches to the version your repository asks for in `.nvmrc`, `.node-version`, `engines` or `volta`, if it is offered and supported. Never to an end-of-life version. |
| **Caches**                | **Clear…** empties the npm, Corepack, pnpm and yarn caches. Your packages and projects are not touched.                                                                                       |

With **Follow the repository** off, a deployment only warns when the repository asks for another version.

## Automate this

**API:** [Update a site's Node.js configuration](https://docs.corefinity.com/api/reference/runtime/update-node-runtime.md), scope `write`

```bash
curl -X PUT https://manage.corefinity.com/api/corestack/sites/1042/node-runtime \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "follow_repository": true,
    "revision": 4
  }'
```

**MCP:** [`corestack_node_version_change`](https://docs.corefinity.com/mcp/tools/corestack_node_version_change.md), scope `write`

```json
{
  "name": "corestack_node_version_change",
  "arguments": {
    "site_id": 4211,
    "revision": 7,
    "major": 24
  }
}
```

**Control Panel:** Managed Websites › your site › Site settings › Software & services ([https://manage.corefinity.com/go/node-runtime](https://manage.corefinity.com/go/node-runtime))

## Related

- [Node.js on Corefinity](/guides/platforms/node-js): See what Node.js is for on a site.
- [Connect a repository](/guides/sites/code-and-deployments/connect-a-repository): Switch a site to Git deployments.
- [Change PHP version](/guides/sites/software-and-services/php-version): Switch a site to another PHP version.
