v27 nightly releases after 2026-09-07 missing from https://nodejs.org/download/nightly/ directory

[MikeMcC399]

• follows on from v27 nightly releases missing from https://nodejs.org/download/nightly/ directory #1018 & ci: update directory cache nightly #1019 (Sep 8, 2026)

The latest v27.0.0 directory listing on https://nodejs.org/download/nightly/ stops at https://nodejs.org/download/nightly/v27.0.0-nightly2026090729667e046b/ from Sep 7, 2026.

https://nodejs.org/download/nightly/index.json on the other hand shows v27.0.0-nightly20260925a3bb551ea7

curl -I https://nodejs.org/download/nightly/v27.0.0-nightly2026090729667e046b/ # results in HTTP 200 success
curl -I https://nodejs.org/download/nightly/v27.0.0-nightly20260925a3bb551ea7/ # results in HTTP 404 failure

whereas

curl -I https://direct.nodejs.org/download/nightly/v27.0.0-nightly2026090729667e046b/ # results in HTTP 200 success
curl -I https://direct.nodejs.org/download/nightly/v27.0.0-nightly20260925a3bb551ea7/ # results in HTTP 200 success

[MikeMcC399]

Also reproducible with n Node.js version manager:

$ n nightly
  installing : nightly-v27.0.0-nightly20260925a3bb551ea7
curl: (22) The requested URL returned error: 404

  Error: download preflight failed for '27.0.0-nightly20260925a3bb551ea7' (https://nodejs.org/download/nightly/v27.0.0-nightly20260925a3bb551ea7/node-v27.0.0-nightly20260925a3bb551ea7-linux-x64.tar.xz)

This is a different issue, caused by the fact that this nightly build was incomplete. See nodejs/build#4480 (comment)

[bmuenzenmeyer]

figure we should keep open until we confirm its resolved on a new nightly

[MikeMcC399]

It's looking good 👍🏻

https://nodejs.org/download/nightly shows additional directories up to https://nodejs.org/download/nightly/v27.0.0-nightly20260925a3bb551ea7/

Testing on Ubuntu 24.04.5 LTS

Utility	Select	Result
https://github.com/actions/setup-node	27-nightly	v27.0.0-nightly20260925a3bb551ea7
https://github.com/tj/n	nightly	v27.0.0-nightly20260925a3bb551ea7

curl -I https://nodejs.org/download/nightly/v27.0.0-nightly20260925a3bb551ea7/ # results in HTTP 200 success

[MikeMcC399]

There appears to be a remaining "Directory not found" issue showing up for v27.0.0-nightly202609268812357aff from 2026-09-26.

https://nodejs.org/download/nightly/index.json shows:

  {
    "version": "v27.0.0-nightly202609268812357aff",
    "date": "2026-09-26",
    "files": [
      "aix-ppc64",
      "headers",
      "linux-arm64",
      "linux-ppc64le",
      "linux-s390x",
      "linux-x64",
      "linux-x64-musl",
      "osx-arm64-tar",
      "osx-x64-pkg",
      "src",
      "win-arm64-7z",
      "win-arm64-zip",
      "win-x64-7z",
      "win-x64-exe",
      "win-x64-msi",
      "win-x64-zip"
    ],
    "npm": "12.1.0",
    "v8": "14.6.202.34",
    "uv": "1.52.1",
    "zlib": "1.3.2.1-motley",
    "openssl": "3.5.8",
    "modules": "147",
    "lts": false,
    "security": false
  },

The directory v27.0.0-nightly202609268812357aff/ is also listed under https://nodejs.org/download/nightly/

Clicking on the directory v27.0.0-nightly202609268812357aff/ in a web browser results in "Directory not found" however.

curl -I https://nodejs.org/download/nightly/v27.0.0-nightly202609268812357aff/ # results in HTTP 404 failure
curl -I https://direct.nodejs.org/download/nightly/v27.0.0-nightly202609268812357aff/ # results in HTTP 200 success

The n Node.js version manager is however able to install nightly for linux-x64:

$ n nightly
  installing : nightly-v27.0.0-nightly202609268812357aff
       mkdir : /home/mike/n/n/versions/nightly/27.0.0-nightly202609268812357aff
       fetch : https://nodejs.org/download/nightly/v27.0.0-nightly202609268812357aff/node-v27.0.0-nightly202609268812357aff-linux-x64.tar.xz
     copying : nightly/27.0.0-nightly202609268812357aff
npm warn cli npm v12.1.0 does not support Node.js v27.0.0-nightly202609268812357aff. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
   installed : v27.0.0-nightly202609268812357aff (with npm 12.1.0)

actions/setup-node is also successful:

Run actions/setup-node@v7
Acquiring 27.0.0-nightly202609268812357aff - x64 from https://nodejs.org/download/nightly/v27.0.0-nightly202609268812357aff/node-v27.0.0-nightly202609268812357aff-linux-x64.tar.gz
Extracting ...
/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/daebea4f-5f5b-4aa7-b299-fd8c45939081 -f /home/runner/work/_temp/279dc7a4-0cf7-4b75-9260-53e45c94fb36
Adding to the cache ...
Done
Environment details
  node: v27.0.0-nightly202609268812357aff
  npm: 12.1.0
  yarn: 1.22.22

[bmuenzenmeyer]

that's the exact behavior a coding agent said would occur (human browsing would still have a gap, programmatic access would succeed) - we have a follow up planned

edit: i'll try to get to this amidst nodeconf eu travel

[MikeMcC399]

that's the exact behavior a coding agent said would occur (human browsing would still have a gap, programmatic access would succeed) - we have a follow up planned

edit: i'll try to get to this amidst nodeconf eu travel

Since neither nvm nor nvm-windows know how to download nightly Node.js releases out-of-the-box, there is a still a gap to be filled by humans. Again, since there haven't been other reports about the nightlies, I would assume low impact, so don't pressure yourself to get a fix in! Your regular TODO list should be fine 🙂 !

[MikeMcC399]

What was the follow-up planned to be and do you have a rough timeframe to get it fixed?