Skip to content

chore: require Node.js 26 LTS - #439

Merged
otaki0413 merged 1 commit into
mainfrom
cursor/node-26-lts-6fa8
Nov 5, 2026
Merged

otaki0413 merged 1 commit into
mainfrom
cursor/node-26-lts-6fa8

Conversation

@otaki0413

Copy link
Copy Markdown
Owner

Why

Move the template from Node.js 24 to Node.js 26 LTS now that 26 is Active LTS.

Node.js Release schedule: 26.x is Active LTS (codename Lithium, initial release 2026-05-05, Active LTS start 2026-10-28, maintenance start 2027-10-20, EOL 2029-04-30). 24.x is Maintenance LTS.

The newest Node 26 LTS patch that is at least one day old is 26.13.0 (released 2026-10-28). There is no 26.13.1 or 26.14.0 on the official release index. The newest @types/node 26.x that satisfies minimumReleaseAge: 1440 is 26.6.6 (published 2026-10-28T18:36:36Z). No newer 26.x exists on npm. minimumReleaseAge is unchanged.

pnpm exec intent list only showed TanStack Router and Start skills. None match a Node version pin, so none were loaded.

Files

File Pin
.github/workflows/ci.yml node-version 24.19.0 → 26.13.0 via voidzero-dev/setup-vp (action still v1.22.0)
package.json added engines.node >=26 (no engines or devEngines field existed). @types/node 24.19.2 → 26.6.6
pnpm-lock.yaml lockfile follows @types/node@26.6.6. Other dependency versions are unchanged; peer keys now resolve against 26.6.6
README.md this template requires Node.js 26 LTS. CI uses 26.13.0. Vite+ itself still documents 22.18+ / 24.11+ / 26+ (and hook floors 22.22.1+ / 24.11+ / 26+); this template does not
AGENTS.md cloud-agent Node guidance and the CI sentence now target 26.13.0

No .nvmrc or .node-version existed, and none was added. No other workflow, devEngines, Wrangler, or docs pin mentioned Node 24.

Unchanged on purpose: @cloudflare/vite-plugin 1.66.0, wrangler 4.156.0, packageManager pnpm@12.16.1, setup-vp v1.22.0, TanStack, React, and vite-plus 1.4.0. Nothing in install, check, test, or build required bumping them.

Workers runtime

Nothing in the Workers runtime config needs to change.

wrangler.jsonc still has compatibility_date 2026-09-16 and compatibility_flags: ["nodejs_compat"]. The deployed runtime is workerd, not the Node.js binary CI uses to install and build. nodejs_compat turns on a subset of Node.js APIs inside that runtime; it is not a Node version pin. For compatibility dates on or after 2026-08-04, Workers already enables that behavior by default, and the existing flag is left as-is. @types/node types the toolchain for TypeScript. worker-configuration.d.ts is generated from wrangler/workerd and did not need a regeneration. Version-specific EOL flags such as remove_nodejs_compat_eol_v24 follow the compatibility date (the v24 flag defaults in 2028-04-30), not the developer Node version.

Verification

Commands ran on Node v26.13.0 with pnpm 12.16.1.

pnpm install — exit 0. Lockfile passed supply-chain policies. @types/node moved from 24.19.2 to 26.6.6.

pnpm check — exit 0.

pass: All 16 files are correctly formatted
pass: Found no warnings, lint errors, or type errors in 7 files

pnpm test — exit 0. Vitest 5.0.5: 1 file passed, 1 test passed.

pnpm build — exit 0. Client and SSR (workerd) bundles built. The build printed a non-failing vite:css-post sourcemap notice (SOURCEMAP_BROKEN) and still exited 0.

pnpm exec vp run cf-typegen --check — exit 0. Wrangler 4.156.0 reported worker-configuration.d.ts is up to date.

Open in Web Open in Cursor 

Move CI, engines, docs, and @types/node onto Node 26 now that 26 is Active LTS. CI pins 26.13.0 and @types/node is 26.6.6.

Co-authored-by: otaki0413.it <otaki0413.it@gmail.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-04T17:56:46.405718Z 467be8e PR opened
🔒 Security Review ✅ Completed 2026-11-04T17:58:07.122053Z 467be8e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@otaki0413
otaki0413 merged commit 5daa82b into main Nov 5, 2026
2 checks passed
@otaki0413
otaki0413 deleted the cursor/node-26-lts-6fa8 branch November 5, 2026 00:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants