Skip to content

breaking: require Node 22.17 - #16597

Merged
Rich-Harris merged 2 commits into
version-3from
bump-node-version
Aug 3, 2026
Merged

breaking: require Node 22.17#16597
Rich-Harris merged 2 commits into
version-3from
bump-node-version

Conversation

@Rich-Harris

Copy link
Copy Markdown
Member

Now that Cloudflare has updated the versions of Node in their build images, we can bump Kit's requirement which allows us to make a small tidy-up.

Don't know if there's any benefit to bumping it further — if there is, now would be a good time to do so

@pkg-svelte-dev

pkg-svelte-dev Bot commented Jul 31, 2026

Copy link
Copy Markdown

Install the latest version of @sveltejs/kit from 80954cb:

pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/80954cbba269d2d68689bca7e7f5cc967a98490b

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/kit/pr/16597

@changeset-bot

changeset-bot Bot commented Jul 31, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 80954cb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@sveltejs/kit Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@svelte-docs-bot

Copy link
Copy Markdown

@Nic-Polumeyv

Nic-Polumeyv commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Same as #16409. No hard feelings, just noting for xref

Looked at later releases. 22.18's type stripping is moot now that Vite loads the config. process.getBuiltinModule (22.3+) could make the async node:async_hooks import in event.js synchronous. Nothing that crazy.

@Rich-Harris
Rich-Harris merged commit c7369a1 into version-3 Aug 3, 2026
24 of 25 checks passed
@Rich-Harris
Rich-Harris deleted the bump-node-version branch August 3, 2026 19:46
Rich-Harris pushed a commit that referenced this pull request Aug 3, 2026
after seeing #16597

---

### Please don't delete this checklist! Before submitting the PR, please
make sure you do the following:

- [x] It's really useful if your PR references an issue where it is
discussed ahead of time. In many cases, features are absent for a
reason. For large changes, please create an RFC:
https://github.com/sveltejs/rfcs
- [x] This message body should clearly illustrate what problems it
solves.
- [ ] Ideally, include a test that fails without this PR but passes with
it.

### Tests

- [x] Run the tests with `pnpm test` and lint the project with `pnpm
lint` and `pnpm check`

### Changesets

- [x] If your PR makes a change that should be noted in one or more
packages' changelogs, generate a changeset by running `pnpm changeset`
and following the prompts. Changesets that add features should be
`minor` and those that fix bugs should be `patch`. Please prefix
changeset messages with `feat:`, `fix:`, or `chore:`.

### Edits

- [x] Please ensure that 'Allow edits from maintainers' is checked. PRs
without this option may be closed.
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.

3 participants