Bump typescript from 6.0.3 to 7.0.2

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

[github-actions]

⚠️ Review required.

Signal	Value
Package	typescript
Update type	version-update:semver-major
Dependency type	direct:development
Compatibility score	38%

This PR requires review because it is either a major version update or has a low compatibility score (< 75%).

[claude]

Claude finished @dependabot[bot]'s task in 2m 3s —— View job

---

Compatibility Assessment

Recommendation: PASS
Risk Level: Low

• Find all imports/usages of typescript in the codebase
• Check release notes for breaking changes (6.x → 7.0)
• Assess whether our usage is affected
• Provide recommendation

Usage in Codebase

typescript is a devDependency only — it is never imported at runtime and never published to consumers.

• package.json:38 — declares "typescript": "7.0.2".
• package.json:32 — build: "tsc" (compile src/ → dist/).
• package.json:33 — test: "vitest --typecheck.enabled --typecheck.checker=tsc" (type-checks tests via tsc).
• No source or test file imports the typescript programmatic API (grep for typescript matches only package.json / package-lock.json). No custom transformers, language-service plugins, or ts-morph-style API consumers exist.
• src/httpResponseErrors.ts uses only core language features: plain class declarations, single inheritance, constructors, a switch, and export. No decorators, no advanced type-level constructs.
• tsconfig.json uses only standard, universally-supported options (target: es2016, module: NodeNext, strict, declaration, sourceMap, esModuleInterop, skipLibCheck).

Because typescript is a build-time tool and the compiled dist/ + .d.ts are what ship, downstream consumers of this published library are unaffected by this bump.

Breaking Changes Analysis

TypeScript 7.0 is the native (Go) compiler port ("Corsa"/tsgo), a rewrite of the 6.x JavaScript-based compiler aimed at ~10× faster builds while targeting behavioral parity with the 6.x type-checker and emitter. The semver-major label and Dependabot's low 38% compatibility score reflect ecosystem-wide risk — primarily for projects that (a) consume the programmatic compiler API or language-service plugins, or (b) rely on less-common CLI flags/config not yet covered by the native port. Neither applies here.

Where the real risk lives for a major TS bump — and our exposure:

• Programmatic API changes → not used. ❌ N/A
• Rarely-supported compiler flags in the native port → we use only mainstream options. ❌ N/A
• Emit / .d.ts differences → possible in principle, but the emitted types here are trivial class declarations. Low concern.
• Stricter type checking on source → source is minimal and already strict. Low concern.

Recommendation Details

PASS / Low risk, supported by concrete evidence rather than the generic compatibility score:

1. ✅ CI is green on this branch — the Node.js CI workflow (run 29242625637) completed successfully with typescript@7.0.2. That workflow runs the tsc type-check (npm test) and the build, so both the compile and type-check paths are already verified under 7.0.2. (Workflow Lint also passed.)
2. ✅ No API surface exposure — typescript is dev-only and its programmatic API is never imported, which is where major-version breakage almost always occurs.
3. ✅ Trivial, standard usage — basic classes + standard tsconfig options that the native port supports.
4. ✅ No consumer impact — dev-only dependency; shipped artifacts (dist/) are unaffected.

The 38% score is an ecosystem-wide heuristic and does not reflect this repo's minimal, dev-only usage.

Optional (nice-to-have): since this library is a small published language, a reviewer may want to glance at the generated dist/httpResponseErrors.d.ts after build to confirm the emitted declarations are unchanged from 6.x. Given the trivial types and green CI, this is not blocking.

Note: I could not run npm ci/tsc locally (dependency install is blocked in this sandbox), so this assessment relies on static analysis plus the already-successful CI run on this branch.
· branch dependabot/npm_and_yarn/typescript-7.0.2

[github-actions]

⚠️ Review required.

Signal	Value
Package	typescript
Update type	version-update:semver-major
Dependency type	direct:development
Compatibility score	38%

This PR requires review because it is either a major version update or has a low compatibility score (< 75%).

[claude]

Claude finished @dependabot[bot]'s task in 1m 3s —— View job

---

Compatibility Assessment

Recommendation: PASS
Risk Level: Low

• Find all imports/usages of typescript in the codebase
• Check release notes for breaking changes (6.x → 7.0)
• Verify build/type-check under 7.0.2 (CI on this branch)
• Provide recommendation

Usage in Codebase

typescript is a devDependency only — never imported at runtime, never shipped to consumers.

• package.json:38 — declares "typescript": "7.0.2" (bumped from 6.0.3).
• package.json:32 — build: "tsc" (compile src/ → dist/).
• package.json:33 — test: "vitest --typecheck.enabled --typecheck.checker=tsc" (type-checks tests via tsc).
• No source or test file imports the typescript programmatic API. A grep for typescript / from "typescript" across **/*.{ts,mts,cts,js,mjs} returns no matches — no custom transformers, language-service plugins, or compiler-API consumers.
• src/httpResponseErrors.ts uses only core language features: plain class declarations, single inheritance, constructors, a switch, and export. No decorators or advanced type-level constructs.
• tsconfig.json uses only standard, widely-supported options (target: es2016, module: NodeNext, strict, declaration, sourceMap, esModuleInterop, skipLibCheck).

The only changed files are package.json (+1/-1) and package-lock.json. The shipped artifacts (dist/ + .d.ts) are unaffected, so downstream consumers of this published library see no change.

Breaking Changes Analysis

TypeScript 7.0 is the native (Go) compiler port ("Corsa" / tsgo) — a rewrite of the 6.x JavaScript-based compiler targeting ~10× faster builds while aiming for behavioral parity with the 6.x type-checker and emitter. The semver-major label and the low 38% Dependabot compatibility score reflect ecosystem-wide risk, concentrated in projects that:

• Consume the programmatic compiler API / language-service plugins → not used here. ❌ N/A
• Rely on less-common CLI flags or config not yet covered by the native port → this repo uses only mainstream options. ❌ N/A
• Emit / .d.ts differences → possible in principle, but the emitted declarations here are trivial class types. Low concern.
• Stricter type checking on source → source is minimal and already strict. Low concern.

None of the high-risk categories apply to this repo. The 38% score is an ecosystem-wide heuristic, not a signal about this codebase's minimal, dev-only usage.

Recommendation Details

PASS / Low risk, backed by concrete evidence:

1. ✅ CI is green on this branch — Node.js CI (run 29242775999) completed successfully with typescript@7.0.2. That workflow runs both the tsc build and the tsc type-check (npm test), so both paths are verified under 7.0.2. Workflow Lint also passed.
2. ✅ No API-surface exposure — typescript is dev-only and its programmatic API is never imported (grep-confirmed), which is where major-version breakage almost always occurs.
3. ✅ Trivial, standard usage — basic classes + a standard tsconfig the native port supports.
4. ✅ No consumer impact — dev-only dependency; only package.json / package-lock.json change.

Optional (non-blocking): since this library is effectively a small published language, a reviewer may want to glance at the generated dist/httpResponseErrors.d.ts after a build to confirm the emitted declarations are byte-for-byte what 6.x produced. Given the trivial types and green CI, this is not required to merge.

Note: I could not run npm ci / tsc locally (dependency install is blocked in this sandbox), so this assessment relies on static analysis plus the successful CI run on this branch.
· branch dependabot/npm_and_yarn/typescript-7.0.2

[github-actions]

⚠️ Review required.

Signal	Value
Package	typescript
Update type	version-update:semver-major
Dependency type	direct:development
Compatibility score	36%

This PR requires review because it is either a major version update or has a low compatibility score (< 75%).

[claude]

Claude encountered an error after 0s —— View job

---

I'll analyze this and get back to you.

[TimJohns]

@dependabot recreate

[github-actions]

⚠️ Review required.

Signal	Value
Package	typescript
Update type	version-update:semver-major
Dependency type	direct:development
Compatibility score	37%

This PR requires review because it is either a major version update or has a low compatibility score (< 75%).

[claude]

Claude finished @dependabot[bot]'s task in 2m 27s —— View job

---

Compatibility Assessment

Recommendation: PASS
Risk Level: Low

• Find all imports/usages of typescript in the codebase
• Check release notes / breaking changes for 6.x → 7.0
• Verify build + type-check under 7.0.2 (CI on this exact commit)
• Provide recommendation

Usage in Codebase

typescript is a devDependency only — never imported at runtime, never shipped to consumers.

• package.json:38 — "typescript": "7.0.2" (was 6.0.3).
• package.json:32 — build: "tsc" (compiles src/ → dist/).
• package.json:33 — test: "NODE_OPTIONS='--trace-deprecation' vitest --typecheck.enabled --typecheck.checker=tsc" — so tsc is also the type-checker for the test suite.
• No programmatic compiler-API usage. Grepping typescript across **/*.{ts,mts,cts,js,mjs,json} (excluding package-lock.json) matches exactly one line: package.json:38. No custom transformers, no language-service plugins, no ts-morph-style consumers.
• src/httpResponseErrors.ts is a single file of plain class declarations with single inheritance and constructors — no decorators, no advanced type-level constructs.
• tsconfig.json uses only mainstream options: target: es2016, module: NodeNext, rootDir: src, declaration, sourceMap, outDir: dist, esModuleInterop, forceConsistentCasingInFileNames, strict, skipLibCheck.

Breaking Changes Analysis

TypeScript 7.0 is the native (Go) compiler port — a rewrite of the 6.x JavaScript compiler targeting ~10× faster builds while aiming for behavioral parity with the 6.x checker and emitter. The semver-major label and low 37% compatibility score are ecosystem-wide heuristics driven by projects that hit the port's rough edges.

The distribution shape changes visibly in this diff: package-lock.json is +368/-7, almost entirely 20 new @typescript/typescript-<platform> optional packages (linux-x64, darwin-arm64, win32-x64, … each with os/cpu constraints) that carry the prebuilt native binaries. That is the expected TS 7 packaging, not a stray transitive pull-in — the only other lock change is the typescript version itself.

Risk categories for a TS major bump, and this repo's exposure:

Risk	Exposure
Programmatic compiler API / LS plugins	N/A — never imported
Uncommon CLI flags / config unsupported by the native port	N/A — mainstream tsconfig only; verified green in CI
Emit / .d.ts differences	Possible in principle; declarations here are trivial class types. Low
Stricter checking on source	Source is minimal and already strict; 0 type errors in CI. Low
Native binary needs a postinstall step	Verified fine — CI uses npm ci --ignore-scripts and tsc still resolved and ran

That last row is the one non-obvious hazard: platform-binary packages sometimes require install scripts, and this repo deliberately installs with --ignore-scripts (.github/workflows/vitest.yml:30). The optional-dependency resolution works without scripts, confirmed empirically below.

Recommendation Details

PASS / Low risk — this is verified, not just inferred. From Node.js CI run 30188451345, job build (24.x) ✅ on this exact commit:

> tsc                                          # build succeeded (~120ms — native compiler)
> vitest --typecheck.enabled --typecheck.checker=tsc
 ✓ test/httpResponseErrors.test.ts (31 tests) 10ms
 Test Files  1 passed (1)
      Tests  31 passed (31)
Type Errors  no errors

So the emit path (tsc → dist/), the type-check path, and the runtime tests all pass under 7.0.2. Workflow Lint also passed.

⚠️ Don't be misled by the skipped check: the pull_request-triggered Node.js CI run (30188452888) shows skipped — that's by design (if: github.event.pull_request.user.login != 'dependabot[bot]' in .github/workflows/vitest.yml:15). The push-triggered run above is the one that actually did the work. Coverage is real.

Supporting reasons:

1. ✅ No API-surface exposure — dev-only, and the programmatic API (where major-version breakage concentrates) is never touched.
2. ✅ Trivial, standard usage — one source file, mainstream compiler options the native port supports.
3. ✅ No consumer impact from the dependency itself — only package.json / package-lock.json change; typescript is not in dependencies or peerDependencies.

Residual gap (non-blocking). Per CLAUDE.md, this library is effectively a small published language, and dist/httpResponseErrors.d.ts is the actual contract consumers compile against. CI proves the build succeeds under 7.0.2, but nothing asserts the emitted declarations are unchanged from 6.x — a silent .d.ts shape difference from the new emitter would pass CI and only surface downstream. Given trivial class types, this is unlikely; a reviewer glancing at the generated .d.ts once after merge closes it. If you'd like a durable guard: Fix this →

Unrelated observation: the npm ci step reports 2 vulnerabilities (1 low, 1 high). Nothing but the TypeScript packages changed in this diff, so this is almost certainly pre-existing on main rather than introduced here — but I couldn't run npm audit to confirm the baseline, so it's worth a separate look independent of this PR.

Note: dependency installation is blocked in this sandbox, so I could not run npm ci / tsc locally. This assessment combines static analysis of the diff, tsconfig.json, and source with the actual CI job log for this commit (build, type-check, and tests all green under 7.0.2).
· branch dependabot/npm_and_yarn/typescript-7.0.2