chore(deps): align workspace typescript devDependencies to ~6.0.3

[kurone-kito]

Summary

• Bump devDependencies.typescript from ~5.9.3 to ~6.0.3 in all
  five workspace packages (example-cli, example-lib, sea-builder,
  typescript-config, vite-lib-config) to match the root
  package.json, which already pinned ~6.0.3
• Refresh pnpm-lock.yaml
• Leave typescript-config's peerDependencies.typescript
  (>=5.7.x) untouched — narrowing it is issue Refine typescript-config's tsconfig.json for TypeScript v7 readiness #111's concern, once
  this floor is in place

Background

typedoc@0.28.20 (pulled in via vite-lib-config) declares a
typescript peer of 6.0.3, but the workspace resolved
typescript@5.9.3 for it — npm ls typescript --all reported it
invalid. Verified before/after: npm ls typescript --all had 20
invalid entries on main, including the typedoc one; after this
change it's down to 17, and none reference typedoc anymore. The
remaining invalid entries are pre-existing, unrelated third-party
peer-range mismatches (e.g. cosmiconfig-typescript-loader,
@microsoft/api-extractor both declaring ^5.2.2) outside this
issue's scope.

pnpm run build, pnpm run lint, and pnpm run test all pass under
TypeScript 6.0.3 — none of this repository's tsconfig.json files use
a setting TypeScript 6.0 deprecated.

Closes #110

Summary by CodeRabbit

• Chores
  • Updated the TypeScript development tooling to version 6.0.3 across the project’s example applications, libraries, and build configuration packages.
  • No user-facing functionality or public APIs were changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a882277a-f18e-467c-adf8-d52c3e431341

📥 Commits

Reviewing files that changed from the base of the PR and between 32da171 and 45c31c6.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• packages/example-cli/package.json
• packages/example-lib/package.json
• packages/sea-builder/package.json
• packages/typescript-config/package.json
• packages/vite-lib-config/package.json

---

📝 Walkthrough

Walkthrough

Five workspace package manifests update their TypeScript development dependency from ~5.9.3 to ~6.0.3. No exported or public entity declarations change.

Changes

Workspace TypeScript alignment

Layer / File(s)	Summary
Update workspace TypeScript requirements packages/example-cli/package.json, packages/example-lib/package.json, packages/sea-builder/package.json, packages/typescript-config/package.json, packages/vite-lib-config/package.json	The five package manifests now require TypeScript ~6.0.3 as a development dependency.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• kurone-kito/builder-config#19: Updates TypeScript dependencies in the same package manifests to ~5.9.3.
• kurone-kito/builder-config#88: Updates TypeScript development dependencies and the repository-wide TypeScript baseline.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	The package updates satisfy the issue, but the required lockfile refresh cannot be verified because pnpm-lock.yaml was excluded by path filters.	Include pnpm-lock.yaml in the review or provide verifiable evidence that the lockfile was refreshed.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the dependency alignment and the target TypeScript version.
Description check	✅ Passed	The description includes a summary, background, affected packages, validation results, and scope boundaries.
Out of Scope Changes check	✅ Passed	The changes are limited to the requested TypeScript devDependency alignment across the five workspace packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch issue/110-align-workspace-typescript

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Aligns all workspace package TypeScript devDependencies to the root-pinned ~6.0.3, primarily to eliminate the typedoc@0.28.20 peer mismatch caused by workspace resolution previously landing on ~5.9.3. This is a maintenance/dependency hygiene change across the monorepo’s build/tooling packages and examples.

Changes:

• Bumped devDependencies.typescript from ~5.9.3 to ~6.0.3 in all five workspace packages.
• Refreshed pnpm-lock.yaml to reflect the new resolution (including typedoc now resolved with typescript@6.0.3).

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Lockfile refresh reflecting TypeScript 6.0.3 in workspace importers and typedoc resolution.
packages/example-cli/package.json	Updates workspace package TypeScript devDependency to ~6.0.3.
packages/example-lib/package.json	Updates workspace package TypeScript devDependency to ~6.0.3.
packages/sea-builder/package.json	Updates workspace package TypeScript devDependency to ~6.0.3.
packages/typescript-config/package.json	Updates TypeScript devDependency to ~6.0.3 while leaving the peer range unchanged.
packages/vite-lib-config/package.json	Updates TypeScript devDependency to ~6.0.3 (relevant to typedoc peer alignment).

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

F4 Cleanup Evidence (server-side fallback via post-merge-cleanup.yml)

Field	Value
Status	applied
Applied	1
Failed	0
Skipped	2
Permission-blocked	0
Posted by	post-merge-cleanup workflow