Skip to content

build(deps-dev): bump @types/node from 20.19.43 to 24.13.3 - #46

Merged
z33b0t merged 1 commit into
mainfrom
deps/types-node-26
Jul 29, 2026
Merged

build(deps-dev): bump @types/node from 20.19.43 to 24.13.3#46
z33b0t merged 1 commit into
mainfrom
deps/types-node-26

Conversation

@z33b0t

Copy link
Copy Markdown
Contributor

Replaces Dependabot's #44, which went to 26.1.2.

Both versions work — I checked. tsc --noEmit is clean and opennextjs-cloudflare build succeeds under 24 and 26. So this isn't a fix, it's a choice about which runtime the type-checker should model.

www.yml pins node-version: 24. Typing the build against Node 26 while running Node 24 is skew in the wrong direction: a call to a Node 26 API would pass tsc locally and fail at build time in CI. Matching the types to the runtime is the boring, defensible default.

The substance of the bump — off @types/node@20, which has been out of support since April 2026 — is unchanged.

If you'd rather track latest, the coherent way to do that is bumping www.yml's node-version and @types/node in the same change. Say the word and I'll do that version instead.

Verification

npx tsc --noEmit # clean
npx opennextjs-cloudflare build # OpenNext build complete.

Same caveat as #45: CI checks nothing here until #38 lands (www.yml has no pull_request trigger).

Closes#44

Dependabot proposed 26.1.2 (#44). It type-checks and builds, but it types the
build against a Node newer than the one we actually run: www.yml pins
`node-version: 24`. Types ahead of the runtime is the wrong direction of skew —
it lets a call to a Node 26 API pass tsc and then fail in CI, which is the one
failure mode this package exists to prevent.
24.13.3 matches the runtime. The 20 -> 24 move is still the substance of the
bump; 20 has been out of support since April 2026.
Verified on both: `tsc --noEmit` clean and a full `opennextjs-cloudflare build`
succeeds under 24 and under 26 — the choice is about which runtime we want the
type-checker to model, not about anything being broken.
If you'd rather track latest, the coherent version of that is bumping www.yml's
node-version and @types/node together; happy to do that instead.
Closes#44
@z33b0t
z33b0t merged commit 576a71a into mainJul 29, 2026
6 checks passed
@z33b0t
z33b0t deleted the deps/types-node-26 branch July 29, 2026 16:45
Sign up for freeto 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.

1 participant

@z33b0t