Node.js 27 Alpha Is Out: What 27.0.0-alpha.0.1.1 Contains, How to Try It, and Why You Should Stay on Node 26 LTS
Node.js 27 alpha builds 27.0.0-alpha.0.1.0 and alpha.0.1.1 are out: what changed, how to install one for testing, CI setup, and why Node 26 LTS stays the one to run.
When we wrote about Node.js 26 becoming LTS and the new yearly release schedule in October, the line for Node 27 read "not released yet". That has changed. The nodejs.org previous-releases page now lists v27 with status Alpha, first released 29 October 2026 and last updated 16 November 2026, and two alpha builds have shipped with release notes: 27.0.0-alpha.0.1.0 on 12 November and 27.0.0-alpha.0.1.1 on 16 November, both prepared by Antoine du Hamel. The site labels 27 "Latest Alpha" next to v26.13.1 as "Latest LTS". This post covers what is in the two builds, what the alpha phase is for, how to install one for testing, what to do in CI, and why the answer to "which Node should I run" is still 26.
What shipped in 27.0.0-alpha.0.1.0 (12 November 2026)
The first alpha with public release notes lists around 194 commits. The notable changes are all marked SEMVER-MINOR; none of them is SEMVER-MAJOR, which is worth noticing: the alpha phase exists so that breaking changes can land early, but the first build is mostly additive.
- child_process: add subprocess.timedOut (#66639). A child process that was killed because its timeout option expired can now say so, instead of leaving you to infer it from the exit signal.
- crypto: make X.509 inspection guards explicit (#67245), and add X.509 generation with CSR support (#67245). This covers generating certificates and certificate signing requests from Node itself rather than shelling out to an external tool.
- dns: coalesce identical concurrent lookup() requests (#62599). Several simultaneous lookups for the same name now share one resolution.
- http: batch body spans per parser execute (#67187), an internal change to how request bodies are handed from the parser to JavaScript.
- sea: generate a compile cache for the VFS modules (#66768), for single-executable applications.
- worker: preload streams into the startup snapshot (#66311), a change on the worker startup path.
What changed in 27.0.0-alpha.0.1.1 (16 November 2026)
Four days later the second alpha followed. Its single notable change is tools: notarize bin/node in the darwin tarballs (#67143), which means the macOS tarball binaries are notarized, so Gatekeeper should stop complaining when you run one unpacked from a download rather than installed from the pkg. The rest of the build is housekeeping: build: enable PIE on Linux (#67386), a dependency bump to nghttp3 1.19.0, several V8 backports, documentation fixes (sqlite number and BigInt binding, X509Certificate invalid validity times, package exports fallback arrays, the value of this in TLS callbacks) and test deflakes.
Note the version string: 27.0.0-alpha.0.1.0 became 27.0.0-alpha.0.1.1. The alpha suffix increments per alpha build; the project has not documented what each digit of the suffix stands for, so do not read a scheme into it. Treat the whole string as the tag you pass to your installer.
What "alpha" means now that Node has one release a year
The October post explained the annual schedule in full, so here is only the sentence that matters, in the project's own words from the releases page: "Starting with Node.js 27, the release cycle will be annual and every major version will move to LTS status after its six-month Current phase (and six additional months of Alpha phase)." In other words, the alpha replaces the odd-numbered release that used to serve as a testing ground. It is signed and tagged like any other build, but it is a prerelease: semver-major changes may land in it at any point until 27.0.0 ships as Current.
The same page spells out the consequence: "Production applications should only use Active LTS or Maintenance LTS releases." The alpha is neither. It is for library maintainers, framework authors, people who run CITGM-style suites against the ecosystem, and anyone who wants to know before April whether their code survives the next major.
How to install the alpha for testing
The builds are published under https://nodejs.org/dist/v27.0.0-alpha.0.1.1/ and the API docs at https://nodejs.org/docs/v27.0.0-alpha.0.1.1/api/. At the time of writing the directory holds Windows x64 and ARM64 installers (msi), a macOS pkg and a darwin-arm64 tarball (the macOS Intel build is marked "coming soon"), Linux tarballs for x64, arm64, ppc64le and s390x, an AIX build and the source archive.
The least surprising route is the tarball: download the one for your platform, unpack it somewhere outside your PATH, and call its bin/node directly or put it first in PATH in one shell. That way nothing on the machine changes for other projects. Version managers can be quicker if they resolve prerelease tags:
# Works if your version manager resolves prerelease tags;
# if it does not, fall back to the tarball above.
nvm install 27.0.0-alpha.0.1.1
fnm install 27.0.0-alpha.0.1.1
# Verify what you are running before you test anything
node --version
# v27.0.0-alpha.0.1.1Whichever way you install it, keep it out of your default shell. A stray nvm alias default pointing at an alpha is how a prerelease ends up in a deploy.
A first look at subprocess.timedOut
Of the notable changes, the one most people will touch is the child_process addition. Until now, when you passed timeout to a spawn call and the limit hit, you had to deduce the cause from the kill signal. The alpha adds a timedOut flag. The snippet below is illustrative and based on the alpha release notes; check the alpha docs for the exact shape before relying on it, because prerelease APIs can still change.
// Illustrative; from the 27.0.0-alpha release notes. Verify against the alpha docs.
const { spawnSync } = require('node:child_process');
const result = spawnSync(process.execPath, ['-e', 'setTimeout(() => {}, 10000)'], {
timeout: 1000,
});
if (result.timedOut) {
console.log('child was killed because the 1 s timeout expired');
} else {
console.log('child exited with status', result.status);
}What to do in CI: an allowed-to-fail row
If you maintain a library, the useful thing to do this week is to add the alpha to your test matrix in a way that cannot block a release. In GitHub Actions that is a separate job with continue-on-error set, or a matrix entry you exclude from required checks. The example below keeps 24 and 26 as the gating jobs and runs 27 as a signal only. Whether actions/setup-node resolves the prerelease tag is something to check on your runner; if it does not, replace the setup step with a step that downloads and unpacks the tarball.
jobs:
test:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
node: [24, 26]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 26
- run: npm ci
- run: npm test
test-node-27-alpha:
runs-on: ubuntu-latest
continue-on-error: true
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 27.0.0-alpha.0.1.1
- run: npm ci
- run: npm testPin the exact alpha tag rather than "27", so a new alpha build does not silently change what the job tests. Bump it by hand when a new build appears and the previous one was green. A red alpha job is information, not an emergency: file an issue upstream if the breakage is in Node, or fix your code if the breakage is yours.
Why you should stay on Node 26 LTS
Node 26 (codename Lithium) is the Active LTS line: first released 5 May 2026, last updated 10 November 2026, and the version the ecosystem's CI matrices target first. It is where security fixes land first for production users: the 11 November security releases shipped as 26.13.1, 24.22.3 and 22.23.5, covered in our post on that release. An alpha build gets no such promise; it gets whatever the next alpha build contains.
- Production services: Node 26 LTS. Node 24 (Krypton) and Node 22 (Jod) are still LTS lines and still receive fixes, but 26 has the longest runway.
- Anything on Node 25: that line reached end of life on 31 March 2026. Move to 26.
- Library and framework maintainers: 26 for releases, 27 alpha in an allowed-to-fail CI job.
- Curious developers: try the alpha in a tarball or a throwaway container, never as your default.
The reason is not that the alpha is unstable in any dramatic way; both builds so far are small and mostly additive. The reason is the contract. An LTS line gets critical bugs fixed for a total of 30 months. An alpha gets replaced. Running it in production means signing up to re-test on every build between now and April.
What to watch next
Two things will tell you how the alpha phase is going. First, the SEMVER-MAJOR column in future alpha release notes: so far it is empty, and the point of the alpha is to fill it early rather than in April. Second, the macOS Intel build, which is still "coming soon" in the 27.0.0-alpha.0.1.1 directory; once it appears the platform set is complete. We will update this series when the next alpha lands with a breaking change worth planning around. Until then: Node 26 to run, Node 27 alpha to test, nothing else to do.