Updated dependencies. - #32
Merged
Merged
Conversation
Minor bumps to playwright, supabase-js, ssr, happy-dom, prettier, the Supabase CLI, svelte, type-fest, and vite, plus vitest 4 to 5. TypeScript stays at 6: svelte-check and kit both still cap it there, and svelte-check is CI's type gate. Vitest 5 needed no source or config changes. It does require node 22.12, so engines moves from >=22 to >=22.12, which engine-strict makes load-bearing. The regenerated database types are a formatting-only change from the newer CLI, committed so CI's drift check passes. Verified against the full CI sequence locally: svelte-check clean, 288 unit tests, 208 e2e tests, 74 Playwright tests, build, and format all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Patch bumps to supabase-js, vite-plugin-svelte, prettier, the Supabase CLI, vite, and vitest. TypeScript stays at 6: svelte-check 4.7.6 and kit 2.70.3 still cap their peer range at ^6. Supabase CLI 2.118 no longer formats `gen types` output (it suggests oxfmt instead), so the regenerated database types are unformatted. They are committed as generated, because CI's drift check compares the file byte for byte and the file is already excluded from prettier. The remaining npm audit warning (cookie <0.7 via kit) predates this change and has no real fix; the suggested --force would downgrade kit to 0.0.30. Verified against the full CI sequence locally: svelte-check clean, 288 unit tests, 208 e2e tests, 74 Playwright tests, build, and format all pass. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Routine dependency maintenance, bumping ten packages and releasing as v0.10.2.
What changed
Minor bumps:
@playwright/test1.63.0,@supabase/ssr0.12.7,@supabase/supabase-js2.116.0,happy-dom20.14.5,prettier3.9.8,supabaseCLI 2.117.0,svelte5.57.1,type-fest5.10.0,vite8.3.0.vitest4 → 5, which needed no source or config changes. Its breaking changes all miss this repo:vi.mockmust now be top level rather than merely warned about, and the two calls inrefresh.test.tsalready are;clearMocksnow defaults to on, and there is novi.fnorvi.spyOnto clear; the rest concern benchmarks, browser mode, coverage, and the-tflag. Per-file@vitest-environmentdocblocks still work, so the two configs stay as they are.engines.node>=22→>=22.12, Vitest 5's floor..npmrcsetsengine-strict=true, so the old range advertised node versions on whichnpm cifails outright. CI already runs node 22.src/database/database.types.tsregenerated. The newer Supabase CLI parenthesizes the conditional types it uses as constraints inTables,TablesInsert,TablesUpdate,Enums, andCompositeTypes. Identical meaning, but CI regenerates the file and fails on any byte difference, so it has to be committed.What was held back
TypeScript stays at 6. 7.0.2 is out, but
svelte-check@4.7.6and@sveltejs/kit@2.70.3both still declaretypescript "^5 || ^6", with no prerelease offering support. CI gates types withsvelte-check, nottsc, so bumping would run the gate against an unsupported compiler. Worth revisiting once the Svelte toolchain declares TS 7 support.Verification
Ran the full
test.yamlsequence locally against local Supabase:svelte-checkclean across 1571 files, 288 unit tests, 208 e2e tests,npm run build, 74 Playwright tests, andnpm run formatreformatted nothing.🤖 Generated with Claude Code