chore(deps): update all dependencies to latest - #357
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
michaelbonner-dev | 3dbde71 | Commit Preview URL Branch Preview URL |
Aug 05 2026, 05:09 PM |
|
Warning Review limit reached
Next review available in: 40 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesDependency updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 47: Update the package.json typescript dependency from ^7.0.2 to ^6.0.2
so the SvelteKit, svelte-check, and TypeScript ESLint setup remains compatible;
only use the documented `@typescript/typescript6` compatibility configuration if
intentionally retaining TypeScript 7.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 70b9ae82-1594-4491-b497-c5e796736e9e
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
package.json
| "tailwindcss": "^4.3.3", | ||
| "tslib": "^2.8.1", | ||
| "typescript": "^6.0.3", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json relevant fields =="
if [ -f package.json ]; then
cat -n package.json | sed -n '1,90p'
fi
echo
echo "== lockfile TypeScript versions =="
if [ -f bun.lock ]; then
rg -n "typescript|vite|svelte|posthog-js|only-allow" bun.lock package.json || true
fi
echo
echo "== tooling/source files =="
git ls-files | rg -i '(^|/)(vite\.config\.(ts|js|mjs|cjs)|svelte\.config\.(js|ts)|tsconfig.*\.json|package\.json|src/.*\.(svelte|ts|js|d\.ts))$' | sed -n '1,200p'
echo
echo "== TypeScript usage / API imports =="
rg -n "from ['\"]typescript['\"]|require\\(['\"]typescript['\"]\\)|typescript\\.|svelte-preprocess|svelte-check|vite-plugin-svelte|`@sveltejs/vite-plugin-svelte`" . --glob '!node_modules' --glob '!dist' --glob '!build' || true
echo
echo "== package scripts =="
python3 - <<'PY'
import json, pathlib
p=pathlib.Path('package.json')
if p.exists():
data=json.loads(p.read_text())
print(json.dumps(data.get('scripts', {}), indent=2))
PYRepository: michaelbonner/michaelbonner.dev
Length of output: 48579
🌐 Web query:
TypeScript 7 stable programmatic API Svelte TypeScript 6 recommended devblogs Microsoft
💡 Result:
As of August 5, 2026, TypeScript 7.0 is the current stable version of the language, having been released by Microsoft in July 2026 [1][2]. TypeScript 7.0 introduces a native Go-based compiler designed to provide significant performance improvements (approximately 10x faster builds) [1][3][2]. However, this version does not yet ship with a stable programmatic API [1][2]. Consequently, many tools in the ecosystem—including those for Svelte, Vue, Astro, MDX, and Angular—cannot fully utilize TypeScript 7.0 for their internal tooling and language services [1][2]. To bridge this gap, Microsoft has published a compatibility package, @typescript/typescript6 [2][4]. This package provides a tsc6 executable and re-exports the TypeScript 6.0 API, allowing developers to run TypeScript 7.0 for builds while permitting tools to rely on the TypeScript 6.0 API for continued support [2][4]. For Svelte, the current recommended version for its toolchain is TypeScript 6.0 [5][6]. Recent Svelte updates (as of May/June 2026) have established TypeScript 6.0 as the minimum required version for SvelteKit and associated language tools [5][7][8]. Svelte maintainers have not yet enabled support for TypeScript 7.0 because of the currently missing stable programmatic API [2]. Microsoft has stated it is a priority to work with these ecosystem projects to support them in future TypeScript releases, with a stable API expected to land in TypeScript 7.1 [1][2][9].
Citations:
- 1: https://www.infoq.com/news/2026/08/typescript-7-released/
- 2: https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/
- 3: https://devblogs.microsoft.com/typescript/
- 4: https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-rc/
- 5: https://svelte.dev/blog/whats-new-in-svelte-june-2026
- 6: feat: typescript 6.0 support sveltejs/language-tools#2985
- 7: https://svelte.dev/blog/whats-new-in-svelte-may-2026
- 8: breaking: make TypeScript 6 the minimum sveltejs/kit#15930
- 9: https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-beta/
Do not merge TypeScript 7 without a compatible setup.
This SvelteKit project uses svelte-check, TypeScript ESLint, and SvelteKit, all of which depend on TypeScript 6 APIs. TypeScript 7.0 does not provide a stable programmatic API, and the installed lockfile ranges for these tools do not include typescript@7.0.2. Keep typescript at ^6.0.2 or use the documented @typescript/typescript6 compatibility setup.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 47, Update the package.json typescript dependency from
^7.0.2 to ^6.0.2 so the SvelteKit, svelte-check, and TypeScript ESLint setup
remains compatible; only use the documented `@typescript/typescript6`
compatibility configuration if intentionally retaining TypeScript 7.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c794e3707
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "tailwindcss": "^4.3.3", | ||
| "tslib": "^2.8.1", | ||
| "typescript": "^6.0.3", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
This bump moves the project to TypeScript 7 while the unchanged Svelte/ESLint toolchain in bun.lock still declares support only for TypeScript 5/6 (@sveltejs/kit and svelte-check) or <6.1.0 (typescript-eslint/@typescript-eslint/parser). In this repo that compiler is used by bun run build, bun run check, and the ESLint config's TypeScript parser, so after installing this lockfile those verification paths run against an unsupported compiler API; the parent version ^6.0.3 satisfied the existing peer ranges. Hold TypeScript at 6.x until the Svelte and typescript-eslint packages are upgraded to versions that explicitly support 7.x.
Useful? React with 👍 / 👎.
Bumps all npm dependencies to their latest versions via `bun update --latest`.
2c794e3 to
3dbde71
Compare
Bumps all npm dependencies to their latest versions using
bun update --latest.lintfailed (exit 1). See PR for details.Summary by CodeRabbit