Skip to content
Tutorials Center
My learning

Topics

Node.js Reference ยท process

Node.js process.release

Reference for process.release in Node.js: the release name, LTS codename and download URLs, and how to tell an LTS build from a current one.

process.release is an object describing the release of Node.js that is running. It always contains the name ('node') and a sourceUrl pointing at the source tarball for this version. On Long-Term Support releases it also has an lts property with the codename, such as 'Krypton' for Node 24.

It is most often used by tools that need to download headers to build native addons (node-gyp reads these URLs) and by diagnostic scripts that want to report whether the runtime is an LTS line.

NODE
console.log(process.release.name); // node
console.log(process.release.lts);  // codename, or undefined on non-LTS

Try it

Node.js Reading the release object

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Node.js Reporting the runtime in one line

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Syntax

NODE
process.release: {
  name: 'node',
  lts?: string,
  sourceUrl: string,
  headersUrl?: string,
  libUrl?: string
}
Property Description
name Always 'node' in official builds.
lts The codename of the LTS line (for example 'Iron', 'Jod', 'Krypton'). Absent on non-LTS releases.
sourceUrl URL of the .tar.gz source for this exact version.
headersUrl URL of the headers-only tarball used to compile addons.
libUrl Windows only: the URL of the node.lib import library (a path set for each architecture).

Returns: a plain object; do not rely on its key order.

Usage notes

  • lts is the test. Check Boolean(process.release.lts) to see whether the runtime belongs to a Long-Term Support line. Production deployments should run LTS.
  • Do not hard-code codenames. New ones are added every October; treat the value as a label for humans.
  • Forks and custom builds may have another name or no URLs. Code that downloads from sourceUrl should handle undefined.
  • Addon builds. Tools like node-gyp use headersUrl to fetch the correct C++ headers; you rarely read it yourself.
  • Not the version number. For comparisons use process.versions.
  • Network. The URLs are informational; reading them does not download anything.
  • Support dates. The object holds no end-of-life date; check the official release schedule for that.