Bump typescript from 5.1.6 to 6.0.3

[dependabot]

Bumps typescript from 5.1.6 to 6.0.3.

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.9.3

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)
• fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

• npm

TypeScript 5.9

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)

... (truncated)

Commits

• 050880c Bump version to 6.0.3 and LKG
• eeae9dd 🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...
• ad1c695 🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)
• 0725fb4 🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...
• 607a22a Bump version to 6.0.2 and LKG
• 9e72ab7 🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...
• 35ff23d 🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...
• e175b69 Bump version to 6.0.1-rc and LKG
• af4caac Update LKG
• 8efd7e8 Merge remote-tracking branch 'origin/main' into release-6.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[greptile-apps]

Greptile Summary

This PR bumps typescript from 5.1.6 to 6.0.3 via Dependabot, a major-version jump that ships several breaking defaults and removes legacy compiler options that this project still relies on.

• Broken tooling peers: typedoc ^0.25.1 only supports TypeScript up to 5.4 (unmaintained); the docs/doc:json scripts will fail. Similarly, @typescript-eslint/parser ^6.4.1 and @typescript-eslint/eslint-plugin ^7.0.0 do not yet have confirmed TypeScript 6.0 support, so linting will break.
• strict now defaults to true: Neither tsconfig sets this explicitly, so upgrading silently enables all strict checks; the build may emit new type errors across the entire codebase.
• moduleResolution: "node" removed: Both tsconfig.json and test/tsconfig.json use this deprecated option, which TypeScript 6.0 now rejects with a compiler error.

Confidence Score: 2/5

Not safe to merge as-is — the build, lint, and docs pipelines all break under TypeScript 6.0 without additional changes to tsconfig files and peer dependencies.

The TypeScript version bump alone does not make this project TypeScript 6.0-ready. The moduleResolution: "node" setting in both tsconfigs will be rejected by the compiler, strict mode will activate for the first time across the entire codebase, typedoc 0.25 is flatly incompatible, and the typescript-eslint packages lack confirmed TypeScript 6.0 support. Multiple scripts (type-check, lint, build, docs) are likely to fail on first run after merging.

package.json drives all the dependency concerns. The unmodified tsconfig.json and test/tsconfig.json also need attention before this upgrade can succeed.

Important Files Changed

Filename	Overview
package.json	Bumps typescript from ^5.1.6 to ^6.0.3 — a major version jump with several breaking changes that the rest of the project hasn't been updated to handle yet (strict-by-default, deprecated moduleResolution, and incompatible tooling peers).
package-lock.json	Lock file updated to pin typescript to 6.0.3 — mechanical change, no independent issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["TypeScript 5.1.6 → 6.0.3 bump"] --> B["strict: true by default"]
    A --> C["moduleResolution 'node' deprecated"]
    A --> D["noUncheckedSideEffectImports: true by default"]
    A --> E["Peer tooling compatibility"]

    B --> B1["tsconfig.json has no explicit strict setting\n→ strict checks now enabled silently"]
    C --> C1["tsconfig.json uses moduleResolution: node\n→ compiler error at tsc / lint time"]
    E --> E1["typedoc ^0.25.1 supports TS ≤ 5.4 only\n→ docs / doc:json scripts fail"]
    E --> E2["@typescript-eslint/parser ^6.4.1\nno confirmed TS 6.0 support\n→ lint fails"]

    style B1 fill:#ffcccc
    style C1 fill:#ffcccc
    style E1 fill:#ffcccc
    style E2 fill:#ffcccc

Loading

Comments Outside Diff (1)

1. package.json, line 102-103 (link)

   @typescript-eslint versions do not yet support TypeScript 6.0

   @typescript-eslint/parser is pinned to ^6.4.1 and @typescript-eslint/eslint-plugin to ^7.0.0. TypeScript 6 support for typescript-eslint is still open (TypeScript 6 Support typescript-eslint/typescript-eslint#12123) and has not landed in the v6/v7 releases. Running npm run lint (eslint --ext .ts) will fail or silently mangle the parse tree because the parser calls internal TypeScript compiler APIs that changed in 6.0. The typescript-eslint packages need to be upgraded to a version that explicitly lists TypeScript 6.0 as a supported peer before this TypeScript bump can be merged safely.

_{Reviews (1): Last reviewed commit: "Bump typescript from 5.1.6 to 6.0.3" | Re-trigger Greptile}

[greptile-apps]

typedoc: "^0.25.1" is incompatible with TypeScript 6.0

TypeDoc 0.25 officially supports TypeScript 4.6 through 5.4 only (it is now unmaintained). Running npm run docs or npm run doc:json against TypeScript 6.0 will fail at runtime because TypeDoc 0.25 does not understand the TypeScript 6 compiler API. TypeDoc 0.28+ is required for TypeScript 5.0–5.8 support, and TypeScript 6.0 support requires an even newer TypeDoc release (tracked in TypeStrong/typedoc#3084). The typedoc and typedoc-plugin-markdown devDependencies must be upgraded before this bump can land.

[greptile-apps]

strict now defaults to true in TypeScript 6.0

Neither tsconfig.json nor test/tsconfig.json sets "strict" explicitly. Under TypeScript 5.x the implicit default was false; TypeScript 6.0 flips this to true, silently enabling strictNullChecks, noImplicitAny, strictFunctionTypes, strictPropertyInitialization, and several other checks at once. Any code that was previously compiling cleanly may now emit errors on the first tsc --noEmit or microbundle build invocation. Either confirm the codebase already passes strict-mode checks (and add "strict": true explicitly), or add "strict": false to tsconfig.json to preserve the previous behaviour.

[greptile-apps]

moduleResolution: "node" is deprecated and removed in TypeScript 6.0

Both tsconfig.json (line 4) and test/tsconfig.json (line 3) use "moduleResolution": "node", which is the old node10 algorithm. TypeScript 6.0 deprecates this option with a compiler error (tracked in microsoft/TypeScript#62200, milestoned for 6.0.0). Running tsc, type-check, or lint after this bump will produce an error on those tsconfig files. The resolution mode should be migrated to "node16", "nodenext", or "bundler" depending on the target environment, and the module settings should be aligned accordingly.