Skip to content

feat: TypeScript 6.0#123

Merged
Rich-Harris merged 4 commits into
mainfrom
feat-ts6
Apr 1, 2026
Merged

feat: TypeScript 6.0#123
Rich-Harris merged 4 commits into
mainfrom
feat-ts6

Conversation

@teemingc

@teemingc teemingc commented Mar 23, 2026

Copy link
Copy Markdown
Member

This PR updates some test directory names and one expected test output. Also bumps the peer range and adjusts the tsconfig.json files to match what ts6 expects

See https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/#up-front-adjustments

Comment thread test/tsconfig.json
"declarationDir": "types",
"declarationMap": true,
"emitDeclarationOnly": true,
"module": "esnext",

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@teemingc teemingc mentioned this pull request Mar 24, 2026
11 tasks
@Rich-Harris Rich-Harris merged commit 4496a4d into main Apr 1, 2026
37 checks passed
@Rich-Harris Rich-Harris deleted the feat-ts6 branch April 1, 2026 01:34
teemingc added a commit to sveltejs/kit that referenced this pull request Apr 1, 2026
closes #15372

This PR extends the SvelteKit peerDep range to include TS 6.0. It also
upgrades our apps/packages using TS purely as a devDependency to use 6.0
(this excludes `kit` because we use TS to generate public types and that
can be a breaking change. `package` is also excluded because it can't
support TS6 until svelte2tsx does).

### TODOs

- [x] update `svelte-check`
sveltejs/language-tools#2988

Required for `@sveltejs/package` if we want to support TS6 in the
future:
- [ ] update `svelte2tsx`
sveltejs/language-tools#2985
- [ ] update `svelte-preprocess`
sveltejs/svelte-preprocess#675

Required for SvelteKit 3 when we switch over to TS6 completely
- [x] update `@sveltejs/eslint-config`
sveltejs/eslint-config#67
- [ ] update `dts-buddy` sveltejs/dts-buddy#123

---

### Please don't delete this checklist! Before submitting the PR, please
make sure you do the following:
- [ ] 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
- [ ] This message body should clearly illustrate what problems it
solves.
- [ ] Ideally, include a test that fails without this PR but passes with
it.

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

### Changesets
- [ ] 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

- [ ] 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.

2 participants