Skip to content

chore: update dependencies + 7d minimum release age#2052

Draft
maxffarrell wants to merge 9 commits into
huntabyte:mainfrom
maxffarrell:chore/update-deps
Draft

chore: update dependencies + 7d minimum release age#2052
maxffarrell wants to merge 9 commits into
huntabyte:mainfrom
maxffarrell:chore/update-deps

Conversation

@maxffarrell
Copy link
Copy Markdown
Contributor

Summary

  • Add min-version-age=7d to .npmrc so pnpm update only upgrades packages published at least 7 days ago (guards against pulling in immediately-yanked releases)
  • Update all workspace dependencies to latest versions (TypeScript 6, Vite 8, Svelte 5.55.5, SvelteKit 2.59.1, Vitest 4, Playwright 1.60, and more)

Notable upgrades

Package Before After
TypeScript ^5.9.2 ^6.0.3
Vite ^7.1.5 ^8.0.12
Svelte 5.46.4 5.55.5
SvelteKit 2.49.5 2.59.1
Vitest ^3.2.4 ^4.1.6
Playwright 1.55.0 1.60.0

Test plan

  • pnpm build:packages passes cleanly
  • Full pnpm build (docs build has a pre-existing Node 26 / velite ESM with { type: 'json' } issue unrelated to this PR)
  • pnpm test:browser — run browser tests against updated deps

🤖 Generated with Claude Code

Add min-version-age=7d to .npmrc so pnpm update only upgrades packages
published at least 7 days ago. Update all dependencies to latest versions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 14, 2026

⚠️ No Changeset found

Latest commit: 5b0a33f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

maxffarrell and others added 3 commits May 13, 2026 23:25
Downgrade vitest, @vitest/browser, and vitest-browser-svelte back to
their v3/v1 series to maintain test stability.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… v4 upgrades

- Fix no-useless-assignment errors: remove redundant null initializers, refactor
  event reassignment in dismissible layer, add eslint-disable for $bindable() rune
  false positives (mounted.svelte, switch-demo-custom.svelte)
- Fix preserve-caught-error: add { cause: error } to thrown errors in build scripts
- Fix shiki v4 breaking change: replace getHighlighter with createHighlighter
- Suppress vite v8/vitest v3 Plugin type conflict in packages/bits-ui/vite.config.ts

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…8, and vitest/vite type conflict

- Fix velite v0.3 double import attributes: skip post-processing if attributes already present
- Fix flexsearch v0.8 API: replace namespace usage with named imports (Index, Id)
- Fix tests/vite.config.ts: import defineConfig from vitest/config to support test property; suppress vite v8/vitest v3 plugin type mismatch

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 14, 2026

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
bits-ui ❌ Failed (View Log) 5b0a33f

@github-actions github-actions Bot requested a deployment to Preview May 14, 2026 04:46 Abandoned
- Upgrade vitest to ^4.1.6, vitest-browser-svelte to ^2.1.1, vite to ^8.0.12
- Add @vitest/browser-playwright package for the new playwright() provider API
- Update vite.config.ts: use playwright() function, maxWorkers instead of poolOptions.forks.maxForks
- Fix type errors from vitest-browser-svelte v2: render() now returns PromiseLike so setup functions use await render()
- Fix Element vs HTMLElement type errors across 13 test files (expect.element() now requires Locator|HTMLElement|SVGElement)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot requested a deployment to Preview May 14, 2026 05:43 Abandoned
Vitest v4 rejects test.environment="browser" when browser.enabled is set.
Remove the redundant environment key; browser.enabled: true is the correct API.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot requested a deployment to Preview May 14, 2026 23:47 Abandoned
Svelte 5.55.5 introduced a change ("don't mark deriveds while an effect is
updating", sveltejs/svelte#18124) that breaks svelte-toolbelt's boxWith()
ref resolution, causing NavigationMenu refs to return a non-Element value
and failing the onFocusOutside/onkeydown guards. Tests pass with 5.55.4.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot requested a deployment to Preview May 15, 2026 01:30 Abandoned
Undo the vitest v4 migration: restore v3 config, test files, and
vitest-browser-svelte v1. Vitest v3 runs with provider: "playwright"
(string) and environment: "browser", which is valid in v3.

Note: vitest@3 declares vite@^7 as a peer; vite@8 is used here under
the same pnpm override pattern established earlier in this branch.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot requested a deployment to Preview May 15, 2026 01:41 Abandoned
With vite 8, svelte-toolbelt's .svelte.js files get pre-bundled by
esbuild (optimizeDeps) before vite-plugin-svelte can transform them,
leaving Svelte runes ($derived, $state) uncompiled and undefined.

Two-part fix:
- optimizeDeps.exclude: ["svelte-toolbelt"] prevents esbuild from
  consuming the files before the Svelte compiler can see them.
- vitePlugin.include: [/node_modules\/svelte-toolbelt/] in svelte.config.js
  opts svelte-toolbelt into vite-plugin-svelte's transform, which is
  normally skipped for node_modules.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot requested a deployment to Preview May 15, 2026 01:52 Abandoned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant