You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bumps Svelte from 5.56.7 → 5.56.8 across every workspace.
Upstream changes
Patch release, two fixes — the first lands directly on a Mochi code path, since the preprocessor auto-wraps every mochi:hydrate* island in a <svelte:boundary>:
fix: call onerror and provide a working reset when hydrating a failed boundary (sveltejs/svelte#18556)
fix: preserve select selection when spread attributes omit value (sveltejs/svelte#18561)
Bump table
Workspace
Field
From
To
packages/mochi
devDependencies
^5.56.7
^5.56.8
packages/mochi-rsvelte
devDependencies
^5.56.7
^5.56.8
packages/site
dependencies
^5.56.7
^5.56.8
packages/demos
dependencies
^5.56.7
^5.56.8
packages/docs
dependencies
^5.56.7
^5.56.8
packages/minimal
dependencies
^5.56.7
^5.56.8
packages/minimal-rsvelte
dependencies
^5.56.7
^5.56.8
packages/support
dependencies
^5.56.7
^5.56.8
Deliberately not changed
packages/mochipeerDependencies.svelte stays at ^5.56.6. It's a floor for published consumers and already admits 5.56.8; raising it would force an upgrade for no API reason. Since published mochi-framework carries Svelte only as a devDependency plus this unchanged peer range, nothing consumer-visible moved — hence chore(deps): rather than fix(deps):, and no release is warranted.
Scope is Svelte only, not a full dependency sweep. Also currently outdated and left alone: @lucide/svelte (1.25.0 → 1.27.0), @rsvelte/vite-plugin-svelte-native (0.2.8 → 0.3.1), svelte-check (4.7.3 → 4.7.4, exact-pinned because it carries a patch keyed on the version), typescript (6.0.3 → 7.0.2).
The bun.lock diff is Svelte-only; the one removed svelte/devalue entry is a dedupe artifact (devalue is now satisfied from the root).
Verification
bun run syncpack — ✅ no issues; cross-workspace agreement holds, including the unchanged peer range.
bun run checks (lint:fix + format + typecheck + test) — ✅ all four stages green. Typecheck 0 errors across all workspaces; tests 142/142 mochi-framework files, 9/9 site, 2/2 support, demos/minimal/minimal-rsvelte all green, 0 failures.
Clean reinstall + dedupe — rm -rf node_modules packages/*/node_modules && bun install. packages/*/node_modules/svelte is empty and node_modules/.bun is absent, so there is exactly one hoisted svelte@5.56.8. (Duplicate copies mean two context maps and break getContext across the island boundary — invisible to CI.)
bun run build — ✅ output byte-identical to the pre-bump baseline apart from timings. No optimization skipped, no shake fallback:
Per-file bundle sizes in the build listing are unchanged too.
Browser smoke test (PORT=4444 bun run dev:site, driven via chrome-devtools):
/ — no console errors/warnings.
/docs/queues/ — no console errors/warnings.
/demos/error-boundaries/ — the demo most relevant to #18556. All five scenarios render their expected fallbacks (user-written boundary, mochi:hydrate SSR throw, mochi:hydrate client throw, mochi:defer server-island throw, healthy server island with an inner throwing mochi:hydrate child). All 22 requests 200, including both /_mochi/island/* fetches. The only console output is the demo's intentional ThrowOnClient failure. Debug bar reports Svelte 5.56.8.
/demos/nested-islands/ — clean console, all four /_mochi/island/* fetches 200.
/demos/is-hydratable/ — clean console, both island fetches 200. This is the canary for the duplicate-copy failure mode (isHydratable() is its first casualty), so it independently confirms the dedupe.
bun run cli-test — ✅ pass (scaffold, install, test, typecheck). minimal and demos both moved and double as create-mochi template sources.
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
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.
Bumps Svelte from 5.56.7 → 5.56.8 across every workspace.
Upstream changes
Patch release, two fixes — the first lands directly on a Mochi code path, since the preprocessor auto-wraps every
mochi:hydrate*island in a<svelte:boundary>:onerrorand provide a workingresetwhen hydrating a failed boundary (sveltejs/svelte#18556)Bump table
packages/mochi^5.56.7^5.56.8packages/mochi-rsvelte^5.56.7^5.56.8packages/site^5.56.7^5.56.8packages/demos^5.56.7^5.56.8packages/docs^5.56.7^5.56.8packages/minimal^5.56.7^5.56.8packages/minimal-rsvelte^5.56.7^5.56.8packages/support^5.56.7^5.56.8Deliberately not changed
packages/mochipeerDependencies.sveltestays at^5.56.6. It's a floor for published consumers and already admits 5.56.8; raising it would force an upgrade for no API reason. Since publishedmochi-frameworkcarries Svelte only as a devDependency plus this unchanged peer range, nothing consumer-visible moved — hencechore(deps):rather thanfix(deps):, and no release is warranted.@lucide/svelte(1.25.0 → 1.27.0),@rsvelte/vite-plugin-svelte-native(0.2.8 → 0.3.1),svelte-check(4.7.3 → 4.7.4, exact-pinned because it carries a patch keyed on the version),typescript(6.0.3 → 7.0.2).The
bun.lockdiff is Svelte-only; the one removedsvelte/devalueentry is a dedupe artifact (devalue is now satisfied from the root).Verification
bun run syncpack— ✅ no issues; cross-workspace agreement holds, including the unchanged peer range.bun run checks(lint:fix + format + typecheck + test) — ✅ all four stages green. Typecheck 0 errors across all workspaces; tests 142/142 mochi-framework files, 9/9 site, 2/2 support, demos/minimal/minimal-rsvelte all green, 0 failures.Clean reinstall + dedupe —
rm -rf node_modules packages/*/node_modules && bun install.packages/*/node_modules/svelteis empty andnode_modules/.bunis absent, so there is exactly one hoistedsvelte@5.56.8. (Duplicate copies mean two context maps and breakgetContextacross the island boundary — invisible to CI.)bun run build— ✅ output byte-identical to the pre-bump baseline apart from timings. No optimization skipped, no shake fallback:svelte-shaker(site)Per-file bundle sizes in the build listing are unchanged too.
Browser smoke test (
PORT=4444 bun run dev:site, driven via chrome-devtools):/— no console errors/warnings./docs/queues/— no console errors/warnings./demos/error-boundaries/— the demo most relevant to #18556. All five scenarios render their expected fallbacks (user-written boundary,mochi:hydrateSSR throw,mochi:hydrateclient throw,mochi:deferserver-island throw, healthy server island with an inner throwingmochi:hydratechild). All 22 requests 200, including both/_mochi/island/*fetches. The only console output is the demo's intentionalThrowOnClientfailure. Debug bar reports Svelte 5.56.8./demos/nested-islands/— clean console, all four/_mochi/island/*fetches 200./demos/is-hydratable/— clean console, both island fetches 200. This is the canary for the duplicate-copy failure mode (isHydratable()is its first casualty), so it independently confirms the dedupe.bun run cli-test— ✅ pass (scaffold, install, test, typecheck).minimalanddemosboth moved and double ascreate-mochitemplate sources.