svelte

Commit Graph

Author	SHA1	Message	Date
Alexander Kireyev	09a67efcfc	fix: warn on undeclared shorthand event handlers on svelte:window/document/body (#18480 ) Same as we already did on regular elements. Fixes #18275 --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	6 hours ago
Hyunbin Seo	44bd73f3e5	docs: replace N-ary times `⨉` with multiplication sign `×` (#18418 ) Replaces the incorrect N-Ary Times Operator `⨉` (U+2A09) with the correct Multiplication Sign `×` (U+00D7) in the box dimension label. Former is intended for mathematical set theory and type theory contexts. For physical dimensions (width × height), `×` is the correct symbol.	7 hours ago
john gravois	793e309d4e	docs: fix typo in basic markup doc (#18434 ) the current example in the docs conflates two different (commonly associated) words. https://www.reddit.com/r/namenerds/comments/1m6yiw6/what_do_we_think_of_the_name_aretha/	7 hours ago
AminBouchareb	07dda4056b	docs: document rune_missing_parentheses compiler error (#18589 )	7 hours ago
Kamil Jakubus	38ef714f1a	fix: scope SSR boundary failed snippets to their boundary (#18593 ) Each `<svelte:boundary>` with: ```svelte {#snippet failed(error)} ... {/snippet} ``` generated a function named failed. Sibling boundaries placed both functions in the same SSR scope: ```js { function failed() {} function failed() {} // Identifier `failed` has already been declared } ``` Resulting in a `[PARSE_ERROR] Identifier `failed` has already been declared` error during build time. A let declaration such as `{const x = 0}` can create a nested lexical block, exposing the collision. The fix gives each boundary its own scope: ```js { function failed() {} $$renderer.boundary({ failed }, ...); } { function failed() {} $$renderer.boundary({ failed }, ...); } ``	7 hours ago
Jared Dunham	f4918d86f3	docs: added generic type parameter example for $state (#18494 )	7 hours ago
Liam O'Dea	f5f70343df	perf: O(n²)→O(n) Map lookups for legacy reactive statements (#18602 )	7 hours ago
Nic Polumeyv	cac27c783e	feat: export RenderOutput, SyncRenderOutput, Csp and Sha256Source from svelte/server (#18648 ) `render` returns `RenderOutput` and takes `csp: Csp`, but both are declared in `src/internal/server/types.d.ts` and never exported. The generated `svelte/server` block has them without `export`, so nothing outside the repo can import them and the docs page names `RenderOutput` as the return type with nothing on the page defining it. Moves them into `src/server/public.d.ts` the way `svelte/motion` went in #17967, rather than re-exporting internals.	7 hours ago
Siddhesh Kabra	faf1e103c5	fix: prevent onoutroend from firing twice when compilerOptions.hmr is true (#18655 ) Fixes #18440 `hmr()` in `packages/svelte/src/internal/client/dev/hmr.js` wrapped a component in a `block` effect containing a `branch` effect. It forwarded the inner effect's `nodes` object to the outer block: This shared the same reference, meaning `outer_block.nodes === inner_branch.nodes`. When `pause_children` collected transitions for unmounting, Each collected transition had `out(check)` called multiple times, starting multiple animations and firing `outroend` multiple times. Fix by only copying `start`/`end` (the DOM range info the outer block needs) without sharing the transitions array:	7 hours ago
Ben McCann	a7ba9e85aa	docs: update mobile FAQ (#18665 ) Updated to mention Symbiote Native --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>	8 hours ago
github-actions[bot]	56a036f4ce	Version Packages (#18640 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.56.10 ### Patch Changes - fix: preserve CSS escape sequences when printing selectors ([#18667](https://github.com/sveltejs/svelte/pull/18667)) - fix: parse `:nth-child(2n of.foo)` where `of` is not followed by whitespace ([#18611](https://github.com/sveltejs/svelte/pull/18611)) - fix: transform expressions inside labeled statements during server compilation ([#18617](https://github.com/sveltejs/svelte/pull/18617)) - docs: clarify that context lookup includes the current component and all ancestors ([#18581](https://github.com/sveltejs/svelte/pull/18581)) - fix: apply CSS custom properties with falsy values on components ([#18634](https://github.com/sveltejs/svelte/pull/18634)) - fix: correctly print `{#await ... catch x}` et al ([#18645](https://github.com/sveltejs/svelte/pull/18645)) - fix: ignore comments of Program node during migration script ([#18656](https://github.com/sveltejs/svelte/pull/18656)) - fix: reliably resolve append_style to its correct root ([#18614](https://github.com/sveltejs/svelte/pull/18614)) - fix: clean up removed capture event handlers from spread attributes ([#18618](https://github.com/sveltejs/svelte/pull/18618)) - fix: don't corrupt renderer type during SSR's legacy `bind:` retry loop ([#18616](https://github.com/sveltejs/svelte/pull/18616)) - fix: treat concise arrow function bodies as implicit returns when calculating blockers ([#18613](https://github.com/sveltejs/svelte/pull/18613)) - fix: give effect teardowns the value from before the first write in a flush ([#18620](https://github.com/sveltejs/svelte/pull/18620)) - fix: avoid double-calling a derived reference when destructuring `$derived` of another `$derived` during server-side rendering ([#18668](https://github.com/sveltejs/svelte/pull/18668)) - fix: preserve namespaces in CSS type selectors ([#18678](https://github.com/sveltejs/svelte/pull/18678)) - fix: increment private state fields through a non-`this` receiver ([#18622](https://github.com/sveltejs/svelte/pull/18622)) - chore: deduplicate client and server context helpers ([#18580](https://github.com/sveltejs/svelte/pull/18580)) - fix: release `last_propagated_event` after event propagation settles so it no longer retains the last event's target subtree ([#18569](https://github.com/sveltejs/svelte/pull/18569)) - fix: allow custom elements to receive async values as props ([#18661](https://github.com/sveltejs/svelte/pull/18661)) - fix: strip comments from inline `style` values in linear time ([#18553](https://github.com/sveltejs/svelte/pull/18553)) - fix: prevent declaration comments from breaking server derived references ([#18641](https://github.com/sveltejs/svelte/pull/18641)) - perf: make async blocker analysis scale linearly with the number of top-level references ([#18549](https://github.com/sveltejs/svelte/pull/18549)) - fix: preserve short-circuiting for logical assignments to private state fields ([#18594](https://github.com/sveltejs/svelte/pull/18594)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	9 hours ago
Scott Wu	5ccdfe3557	docs: note comments within tags possibility (#18482 ) Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	12 hours ago
Joe Schafer	545205b420	perf: make async blocker analysis linear (#18549 ) `trace_references` recreated a fresh seen set for every CallExpression, so `touch` re-walked the same transitive assignment graph once per call. For N calls reaching an N-deep binding chain, this was $O(N^2)$. Share one seen set per trace_references invocation. Use separate sets for the write-directed CallExpression touches and the read-directed ReturnStatement touches. The shared set ensures each assignment-value expression is walked at most once, making the traversal linear. `touch` only ever adds to a fixed target set, so skipping an already-seen expression never drops a binding: compiler output is byte-identical. Complements #18548. --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	13 hours ago
Mukund Sarma	950e2a837c	fix: strip comments from inline style values in linear time (#18553 ) `to_style()` strips CSS comments from an inline `style` value with `/\s\/\.?\\/\s/g`. The leading `\s` makes the match retry from every position, so a long run of whitespace backtracks in O(n^2). When a dynamic `style={value}` sits on an element that also has a `style:` directive, that regex runs on `value`, so a large whitespace string can stall rendering (server) or the main thread (client). ### Fix Drop the surrounding `\s` and match only the comment: `/\/\.?\\//g` to prevent quadratic regex. The surrounding whitespace was already removed by the `.trim()` --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	13 hours ago
randalmurphal	ffc0e6e7ef	fix: release last_propagated_event after event propagation settles (#18569 ) Fixes #18568 `last_propagated_event` was added in #16527 to stop Firefox from garbage collecting the event wrapper mid-propagation. The problem with this is that the even is now retained until the next event, which could be a while. This removes it after a macrotask. Co-authored-by: rmurphy <rmurphy@fortressinfosec.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>	13 hours ago
jyc.dev	f159e14de7	chore: switch to @changesets/changelog-github (#18570 ) Switch `@svitejs/changesets-changelog-github-compact` to `@changesets/changelog-github` (its new `template` option reproduces the same compact output).	14 hours ago
Nic Polumeyv	2f684fefd7	docs: clarify that context lookup includes the current component and all ancestors (#18581 ) Fixes #7916. Context lookup starts at the current component, not the closest parent. `setContext` followed by `getContext` with the same key in the same component returns the value. --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	15 hours ago
Nic Polumeyv	3feb34a992	chore: deduplicate client/server context helpers (#18580 ) The server copy of `createContext` shipped without the `missing_context` throw and #17580 had to hand-mirror the client body back in, so this duplication has already cost a bug. This moves the realm-independent parts, the `createContext` tuple, `get_parent_context`, and `get_or_init_context_map`, into `internal/shared/context.js`, and each realm keeps its public context functions as thin wrappers over its own state.	15 hours ago
Rudevin	388840b1b2	docs: note that transitions bypass CSS prefers-reduced-motion (#18597 ) --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	15 hours ago
kdelay	24130c18e2	fix: parse nth-child `of` syntax without whitespace after `of` (#18611 ) Fixes #18609 A `<an+b> of <selector>` CSS statement does not need whitespace after `of` if it's followed by a CSS-known syntax (like a `.` which marks a class identifier). Adjust the regex accordingly.	15 hours ago
Magnar Ovedal Myrtveit	a166761b04	fix: treat concise arrow function bodies as implicit returns when calculating blockers (#18613 ) Fixes #18612. A concise arrow body does not contain a `ReturnStatement` which we traverse in full calculate_blockers (else we bail on functions), so short-cut to `touch` there. --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	15 hours ago
Sander Machado	a4c60ccdbb	fix: append_styles resolving to `document.head` in WC (#18614 ) Fixes #18288 Check the surrounding branch effect's start node to retrieve the correct root node instead of just the anchor, since the latter could come from each.js/branch.js and be a text node that is never going to get connected --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	15 hours ago
Nathan Asdarjian	ee1249b43c	fix: preserve renderer type in copy() during SSR (#18616 ) Fixes #18404 `<svelte:head>` combined with two or more components that each use `bind:` on a child component's prop corrupts a renderer's `.type` during SSR, misplacing the head hydration marker in `<body>` instead of `<head>`. Reason: `copy()` (`packages/svelte/src/internal/server/renderer.js`) rebuilds via `new Renderer(this.global, this.#parent)`. That constructor defaults `.type` from the parent's current type, not from `this.type`. To fix it we therefore reassign it (like already do for the boundary elsewhere)	18 hours ago
svelte-triage-bot[bot]	9c2494b134	fix: preserve namespaces in CSS type selectors (#18678 ) Fixes #18677. - preserve namespace prefixes on CSS `TypeSelector` AST nodes - accept wildcard local names in `svg\|` and `\|*` - retain namespaces when printing modern ASTs - keep namespaced universal selectors intact while adding scoped CSS selectors - add compile and print regressions covering all four namespace forms --------- Co-authored-by: svelte-triage-bot <team@svelte.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	20 hours ago
Madan kumar	19aa51d443	fix: print `{#await ... catch}` et al correctly (#18645 ) needs to check the error value, not the then value --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	1 day ago
Marwan	8835003d41	fix: preserve CSS escape sequences when printing selectors (#18667 ) Fixes #18664 `print()` was writing selector names back out verbatim. The parser decodes CSS escape sequences when it reads them — `\31` becomes `1`, `\a` becomes a newline — so the printer produced selectors that either failed to re-parse (`#123`) or silently meant something different (`#line\nbreak` turns into a descendant combinator). A small re-escaper (`escape_identifier`) is now used when printing type, class, id, pseudo, attribute and at-rule names. Also fixes a backslash parser bug in the process. --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	1 day ago
Gautier Ben Aïm	fe4a56b0a8	fix: avoid double-calling a derived reference when destructuring (#18668 ) Hi! This PR fixes #18666 ### Before submitting the PR, please make sure you do the following - [x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [x] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`. - [x] This message body should clearly illustrate what problems it solves. - [x] Ideally, include a test that fails without this PR but passes with it. - [x] If this PR changes code within `packages/svelte/src`, add a changeset (`npx changeset`). ### Tests and linting - [x] Run the tests with `pnpm test` and lint the project with `pnpm lint`	2 days ago
subotac	384ee73aa2	fix: preserve logical assignments to private state fields (#18594 ) Fixes #18592. Logical assignments to private `$state` fields were compiled as unconditional setter calls. This preserves JavaScript short-circuiting by evaluating the setter only when `\|\|=`, `&&=`, or `??=` should assign. The regression sample covers the no-assignment branch for all three operators, alongside the existing assignment-path coverage. ### Before submitting the PR, please make sure you do the following - [x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [x] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`. - [x] This message body should clearly illustrate what problems it solves. - [x] Ideally, include a test that fails without this PR but passes with it. - [x] If this PR changes code within `packages/svelte/src`, add a changeset (`npx changeset`). ### Tests and linting - [x] Run the tests with `pnpm test` and lint the project with `pnpm lint`	2 days ago
Siddhesh Kabra	a5ea12ee93	fix: skip Program comment nodes in migration to prevent crash (#18656 ) Fixes #18304 The parent of a declaration could be the Program, on which HTML comments are added, which subsequently crashes the funciton. Ignore such comments. --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	3 days ago
Gautier Ben Aïm	9414eaa41b	fix: prevent crash on async custom element attributes (#18661 ) attributes setter logic wasn't async-aware --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	3 days ago
Yuichiro Yamashita	248a2e1db4	fix: transform expressions inside labeled statements during server compilation (#18617 ) close: #18615	3 days ago
subotac	c0987c09f8	fix: remove stale capture listeners from spread attributes (#18618 ) Fixes #18608. When `set_attributes` normalized removed spread attributes, it also copied its internal `$$` listener bookkeeping keys into `next` with a `null` value. This cleared the stored callback before event cleanup, so removing a capture handler passed `null` to `removeEventListener` and left the listener attached. Skip internal `$$` keys during missing-attribute normalization. The updated runtime-runes sample verifies replacing and then removing a spread capture handler in both client and hydration modes. --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	6 days ago
Yuuki Oohara	a224dd5867	fix: give effect teardowns the value from before the first write in a flush (#18620 ) Fixes #18619 Make sure to not override old values with newer values that are part of the same flush --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	7 days ago
svelte-triage-bot[bot]	221dcae8ca	fix: preserve comment placement for server derived reads (#18641 ) Fixes https://github.com/sveltejs/svelte/issues/18607. For server output, `build_getter` reused a derived binding's declaration identifier as the generated call callee. Esrap therefore associated leading declaration comments with an earlier reference, potentially emitting them immediately after `return` and triggering automatic semicolon insertion. The getter returned `undefined` instead of the derived value. Fix it by avoiding the double-transform. --------- Co-authored-by: svelte-triage-bot[bot] <316883489+svelte-triage-bot[bot]@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	7 days ago
남정욱	7725f77cca	fix: apply CSS custom properties with falsy values on components (#18634 )	7 days ago
Yuichiro Yamashita	135f4439c3	fix: increment private state fields through a non-`this` receiver (#18622 )	7 days ago
github-actions[bot]	20b341f100	Version Packages (#18628 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.56.9 ### Patch Changes - fix: skip controlled each fast path while another batch is pending ([#18625](https://github.com/sveltejs/svelte/pull/18625)) - fix: better whitespace handling inside printer ([#18638](https://github.com/sveltejs/svelte/pull/18638)) - fix: don't duplicate comments in attributes ([#18636](https://github.com/sveltejs/svelte/pull/18636)) - fix: preserve CSS comments in the AST printer ([#18637](https://github.com/sveltejs/svelte/pull/18637)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	1 week ago
Simon H	ee6dff80ca	fix: better whitespace handling inside printer (#18638 ) - preserve whitespace around elements if it leads to a line break - preserve whitespace for whitespace-sensitive elements (pre, textarea, title) Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 week ago
Simon H	a1d5035d17	fix: preserve CSS comments in the AST printer (#18637 ) Adds a new `comments` array to the stylesheet node which CSS comments are added to. Is subsequently used in `print` to see them in the output. Alternative to #18475	1 week ago
Simon H	3ed9db4ba7	fix: don't duplicate comments in attributes (#18636 ) An attribute with a comment would be printed again atop the following attribute because we didn't take that case into account.	1 week ago
Sankalp Thakur	26786e9298	fix: skip controlled each fast path while another batch is pending (#18625 ) Fixes #18610 ### Problem In async mode, a controlled keyed `{#each}` throws `TypeError: Cannot read properties of undefined (reading 'e')` when its collection becomes empty while an earlier batch is still pending on the same block. The fast path in `pause_effects` cleared `state.items` and then called `destroy_effects`, which walks pending batch keys and reads `state.items.get(key).e`. Those EachItems are still needed for the pending batch (preserved offscreen), so clearing the map makes the dereference throw and aborts the commit mid-flight. ### Fix Only take the controlled-each fast path when `state.pending.size === 0`, so pending batches keep their items until they commit or discard.	2 weeks ago
github-actions[bot]	44a7813730	Version Packages (#18572 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.56.8 ### Patch Changes - fix: call `onerror` and provide a working `reset` when hydrating a failed boundary ([#18556](https://github.com/sveltejs/svelte/pull/18556)) - fix: preserve select selection when spread attributes omit value ([#18561](https://github.com/sveltejs/svelte/pull/18561)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	4 weeks ago
Elliott Johnson	23bc246a99	chore: Supply chain hardening (#18253 ) `svelte` Supply-chain hardening pass. ## Changes - Bump `packageManager` from `pnpm@10.4.0` to `pnpm@10.33.4` with `+sha512` integrity suffix. - Add to `pnpm-workspace.yaml`: - `minimumReleaseAge: 1440` - `minimumReleaseAgeExclude: ['@sveltejs/*', svelte, esrap, devalue]` - `blockExoticSubdeps: true` - Remove `pkg.pr.new.yml` workflow in favor of `pkg.svelte.dev` - Pin all third-party GitHub Actions to full SHA with `# vX.Y.Z` comments across `ci.yml`, `autofix.yml`, `release.yml`, `ecosystem-ci-trigger.yml` - Upgrade `pnpm/action-setup` references in `ci.yml`, `autofix.yml`, `release.yml` from a SHA that was incorrectly labeled `# v4` (actually `v5.0.0` / `v4.4.0`) to the current `v6.0.8` SHA so the version label matches reality.	4 weeks ago
Nic Polumeyv	3dde011d3a	fix: call `onerror` and provide a working `reset` when hydrating a failed boundary (#18556 ) Fixes #18555 A boundary that failed during SSR hydrates via `#hydrate_failed_content`, which never calls `onerror` and passes the `failed` snippet a no-op `reset`. Both came in with #17672, whose docs say `onerror` "will be called upon hydration with the deserialized error object". Once hydrated as failed, the boundary can never leave that state. Downstream this is what keeps SvelteKit's `+error.svelte` mounted after navigating away from a server-rendered error page (sveltejs/kit#16345). This extracts the reset/onerror machinery from `#handle_error` into `#create_reset` and uses it in the hydration path too. `onerror` is invoked in a microtask because it may mutate state, which is disallowed while hydrating. `#handle_error` already invokes it asynchronously, so the timing matches the error path. The tests flip a `recovered` flag before calling `reset`, since the child would otherwise throw again. That is the intended retry pattern, and the same one kit uses when it resets route boundaries on navigation. Verified against kit end to end, hydrating a server-rendered error page and navigating away now tears it down with no kit changes needed.	4 weeks ago
Floze	2bace308e3	fix: preserve select selection with spread attributes (#18561 ) Fixes #18557 A `<select>` with spread attributes initializes the option mutation observer even when those attributes never provide a `value`. In that case the element has no internal `__value`, but the observer previously treated the missing property as an explicit `undefined` value and deselected every option after an option was added or removed. Only reapply the programmatic selection when `__value` is actually present. This preserves the browser's current selection for spreads without a value while keeping the existing behavior for bindings, including an explicitly stored `undefined` value. A runtime-legacy regression fixture covers both adding and removing an option in client and hydration modes. ### Before submitting - [x] References the existing issue - [x] Uses a `fix:` title - [x] Includes a regression test - [x] Includes a patch changeset for `svelte` ### Test plan - [x] `FILTER=select-spread-preserve-selection pnpm test runtime-legacy --maxWorkers=1` (2 tests passed: client and hydrate) - [x] `git diff --check` - [ ] Full `pnpm test` was not run because the shared host was under resource pressure and broad test processes were explicitly avoided - [ ] `pnpm lint` and `pnpm check` were not run for the same reason - [ ] Targeted repository Prettier check was attempted, but could not start because `prettier-plugin-svelte` required the ungenerated `packages/svelte/compiler/index.js`; no broad build or dependency reinstall was run ### AI disclosure AI-assisted: the implementation, regression test, and pull request text were prepared with OpenAI Codex and reviewed by the contributor. Co-authored-by: Paolo Ricciuti <ricciutipaolo@gmail.com>	4 weeks ago
github-actions[bot]	b29d7002ec	Version Packages (#18560 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.56.7 ### Patch Changes - chore: provide `indent` option for `print` ([#18474](https://github.com/sveltejs/svelte/pull/18474)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	1 month ago
Rich Harris	d9e40d17cf	docs: update link on hooks page (#18564 ) this docs page updated recently and broke everything	1 month ago
Manuel	b791cac54e	chore: provide `indent` option for `print` (#18474 ) Relevant for https://github.com/sveltejs/cli/pull/1138. This is basically just an option from `esrap` that we pass through. That will allow tools like `sv migrate` to provide a guessed indent based on the other file contents and therefore allow us to produce way smaller diffs. Since we are just passing an option, there is no need for a test here. Technically a `feat:` but i dont think this is relevant enough. ### Before submitting the PR, please make sure you do the following - [x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [x] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`. - [x] This message body should clearly illustrate what problems it solves. - [ ] Ideally, include a test that fails without this PR but passes with it. - [x] If this PR changes code within `packages/svelte/src`, add a changeset (`npx changeset`). ### Tests and linting - [x] Run the tests with `pnpm test` and lint the project with `pnpm lint`	1 month ago
github-actions[bot]	4a6a85b5f1	Version Packages (#18552 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.56.6 ### Patch Changes - perf: skip unnecessary blocker analysis when compiling components without top-level await ([#18548](https://github.com/sveltejs/svelte/pull/18548)) - fix: rerun derived that had an abort controller on reconnection ([#18551](https://github.com/sveltejs/svelte/pull/18551)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	1 month ago
Joe Schafer	d0dbe1a480	perf: skip quadratic blocker analysis when no top-level await (#18548 ) Skip function reference tracing in `calculate_blockers` when a component has no top-level `await`. Blockers only represent dependencies on top-level async statements. Without a top-level `await`, no binding can have a blocker, so tracing every top-level function cannot affect the generated output. In large components with many functions and transitive assignments, that unnecessary work can become quadratic.	1 month ago

1 2 3 4 5 ...

11326 Commits (main) All Branches Search

11326 Commits (main)

All Branches