Bump typescript from 5.9.3 to 7.0.2 - #424
Conversation
dependabot
Bot
added
dependencies
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 7.0.2. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](https://github.com/microsoft/TypeScript/commits) --- updated-dependencies: - dependency-name: typescript dependency-version: 7.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
34d6d9d to
4324b98
Compare
|
Closing in favor of #429, which bumps to TypeScript 6.0.3 instead. TypeScript 7 can't land yet: it's the native Go compiler and doesn't expose a public compiler API, so anything doing The Worth reopening as a straight one-line bump once typescript-eslint ships TS 7 support. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Supersedes #424, which bumped straight to TypeScript 7.0.2. That cannot land yet: typescript-eslint has no TS 7 support and is blocked upstream until the native Go compiler ships a public API (typescript-eslint/typescript-eslint#10940), so `npm run lint` crashes in ts-api-utils. TypeScript 6 is the last JS-based compiler and sits inside typescript-eslint's `<6.1.0` peer range. TypeScript 6 turns several tsconfig options into deprecation errors and drops automatic `@types` inclusion, so the config needs three changes: - `baseUrl` is deprecated and removed in 7.0; `rootDir` replaces it and has to be explicit once `baseUrl` is gone - `paths` values must be relative in 7.0 - `types: ["chrome"]` restores the `chrome` globals, which 5.9 picked up by scanning all of node_modules/@types Also refreshes @types/node 24.0.8 -> 26.1.2 in the lockfile. 24.0.8 declares `URLPattern` incompatibly with TypeScript 6's lib.dom.d.ts, which this project sees because it sets `skipLibCheck: false`. @types/tape already requests `@types/node: "*"`, so no direct dependency is needed. The emitted `distribution/` is byte-identical to the 5.9.3 output across all 108 files, so the published API is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Supersedes #424, which bumped straight to TypeScript 7.0.2. That cannot land yet: typescript-eslint has no TS 7 support and is blocked upstream until the native Go compiler ships a public API (typescript-eslint/typescript-eslint#10940), so `npm run lint` crashes in ts-api-utils. TypeScript 6 is the last JS-based compiler and sits inside typescript-eslint's `<6.1.0` peer range. TypeScript 6 turns several tsconfig options into deprecation errors and drops automatic `@types` inclusion, so the config needs three changes: - `baseUrl` is deprecated and removed in 7.0; `rootDir` replaces it and has to be explicit once `baseUrl` is gone - `paths` values must be relative in 7.0 - `types: ["chrome"]` restores the `chrome` globals, which 5.9 picked up by scanning all of node_modules/@types Also refreshes @types/node 24.0.8 -> 26.1.2 in the lockfile. 24.0.8 declares `URLPattern` incompatibly with TypeScript 6's lib.dom.d.ts, which this project sees because it sets `skipLibCheck: false`. @types/tape already requests `@types/node: "*"`, so no direct dependency is needed. The emitted `distribution/` is byte-identical to the 5.9.3 output across all 108 files, so the published API is unchanged. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 participant
Bumps typescript from 5.9.3 to 7.0.2.
Release notes
Sourced from typescript's releases.
Commits
Maintainer changes
This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.