11392 Commits (message-box)

 

All Branches   

Search

Author	SHA1	Message	Date
ChaseCopeland	15720b16a5	docs: Updated docs to include information on easing functions (#16070) ... closes #15992 This is a minor update to the easing documents. It adds an overview description for the module and short descriptions for each of the easing functions. --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 weeks ago
sliang-code	63b4c3652d	fix: don't apply scoped CSS class to elements inside <svelte:head> (#18160) ... skip elements inside head, they should not get hashes --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 weeks ago
PD Shaheed Ali Khan	2ac7366391	perf: optimize simple object destructuring in @const tags (#18390) ... This PR resolves a `TODO` in `ConstTag.js` regarding the optimization of simple object pattern matching cases like `{@const { x } = y}`. --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
Nic Polumeyv	a6560bbe08	fix: don't resurrect outroing elements when an ancestor block is paused and resumed (#18431) ... Fixes #15604 Given two nested blocks that both transition: ```svelte {#if fetching} <p>loading</p> {:else} <div transition:fade> {#if shown} <div class="red" transition:fade|global>red square</div> {/if} </div> {/if} ``` and this sequence, where each step happens before the previous fade finished: ```js shown = false; // red square starts fading out fetching = true; // outer block starts fading out too fetching = false; // 50ms later ``` the red square should finish fading out and be removed, since `shown` is still false. Instead it fades back in and stays on screen: resuming the outer block walks the whole subtree, clears `INERT` on every effect and plays `in()` on every transition it finds — including the inner block's, so the square's outro is aborted and the removal callback waiting on it never runs. The inner block has no reason to re-run on its own, `shown` never changed again. The root issue is that `INERT` records no ownership — it can't distinguish "paused by the ancestor currently being resumed" (revive) from "paused by its own block for its own reasons" (leave alone). The pause side already has this restraint: `pause_children` refuses to touch a subtree that is already `INERT`. The resume side had nothing to check. This PR marks the one effect `pause_effect` was actually called on — the root of the paused subtree — with a `PAUSED` flag, and gives resume the same restraint: ```js function resume_children(effect, local) { if ((effect.f & PAUSED) !== 0) return; ``` so a resume can only ever undo its own pause; the flag is only cleared by `resume_effect` on that exact effect. If `shown` flips back to true while the outer block is paused, this still works: the inner block effect carries no `PAUSED` itself, so it is resumed and rescheduled, re-evaluates its condition and revives its own branch.	2 weeks ago
dependabot[bot]	78979c87c9	chore(deps-dev): bump vite from 7.3.2 to 7.3.5 (#18444)	2 weeks ago
svelte-triage-bot[bot]	a6153f1d2a	fix: preserve whitespace after inline elements when printing (#18685) ... Fixes #18683. The printer previously trimmed leading whitespace after an inline element and failed to replace it when the fragment stayed on one line. Track that whitespace while grouping fragment nodes and emit a space for inline output, while retaining newline-based separation for multiline output. Adds regression coverage for whitespace following an inline element and updates existing print snapshots that exposed the same behavior.	2 weeks ago
Nic Polumeyv	3b559bbf96	fix: avoid NaN keyframe values in slide transition (#18430) ... Fixes #14205 When a `slide` transition runs on an element without a layout box, for example inside a `display: none` parent, `getComputedStyle` returns values like `auto` for the animated dimensions. These were passed through `parseFloat` unguarded, so the generated css contained `height: NaNpx` and the browser rejected the keyframe property with an "Invalid keyframe value" warning on every transition. Fix it by omitting properties if they have unparseable numbers - it's the same outcome but you don't see a warning. --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 weeks ago
adiGuba	3405b5e735	fix: distinct memoizer on style/class directives (#18466) ... Fix #18465 The style and classe directives are generated using an unique memoizer for all the class/style directive, which means if you have multiple of the same time on one element you have overly broad invalidation/reruns. This fixes it by having one memoizer call per directive instead of collecting them. --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
Giorgio Maria Federico Birnthaler	a1ec9c8eb7	chore: fix typo in read_version JSDoc (#18470)	2 weeks ago
Rupankar Dutta	224fcadbd5	fix: route $derived teardown errors through invoke_error_boundary (#18486) ... Fixes #18485 Two parts to this: 1. explicitly invoke error boundary during teardown errors, else they go missing/bubble up outside the render tree 2. skip destroying/destroyed boundaries will searching a handler --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
Barry	8bf9ec8700	docs: clarify $bindable fallback binding requirement (#18477)	2 weeks ago
Paolo Ricciuti	06c9b7929a	fix: prevent `selectedcontent` mutation from changing the selected option (#18495) ... Basically, in a situation like this ```svelte <script lang="ts"> let value = $state('A'); </script> <input oninput={() => {}} /> <select bind:value> <button><selectedcontent></selectedcontent></button> <option>A</option> <option>B</option> <option>C</option> </select> <style> select,::picker(select){ appearance: base-select; } </style> ``` what happens is that the `oninput` is delegated and so it registers the global listener (which means it listen on every `oninput` not just the one from the input). When the select change, the `input` event is dispatched first, the listener runs, doesn't find an `__input` handler and returns. Now before the `change` event is emitted, the `MutationObserver` in `init_select` is triggered by the browser updating `selectedcontent` and invokes `select_option` with `select.__value`. However, since the `change` event has yet to fire, `select.__value` still has the old value, so we "reselect" that. When the change event runs, the selected option is effectively the old one and the whole thing breaks. I had to add the test in `runtime-browser` because JSDom doesn't support `selectedcontent`	2 weeks ago
Nic Polumeyv	b2a24b0426	fix: run `onDestroy` callbacks when a server render throws (#18585) ... Fixes #18584. There's multiple parts to this - abort signal was buggy. It wasn't scoped per render, so cross-talk was possible. Fix by scoping to renderer - onDestroy callbacks were skipped when something throws. Fix by carefully aborting the rest of the tree, waiting for settle, collect all callbacks and then call them --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 weeks ago
Nic Polumeyv	6266debb21	docs: clarify when `$effect.pre` runs relative to DOM updates (#18534) ... Related to #16648 - describe the `$effect.pre` in more detail --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
Nic Polumeyv	9d0062d607	fix: make template store subscriptions wait for the promise that assigns the store (#18582) ... Blockers didn't include analyzing implicit store subscriptions, which could also only happen in the template. Also needs to defer store unsubscribe until after the async template has settled in case the store value is read after an async blocker, in which case unsubscribe synchronously is too soon. Fixes https://github.com/sveltejs/kit/issues/15119	2 weeks ago
Khaled Waleed	2d2e5df26e	fix: don't turn component instances stored in $state into state proxies (#18646) ... Fixes #18416. We previously said that we don't want to handle component instances specifically when they're wrapped with state in #16747 - though the use case presented back then was much more arcane than the one in #18416. Therefore we now don't proxify component instances anymore, which also makes the dev time proxy warning obsolete. --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
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>	2 weeks 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.	2 weeks 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/	2 weeks ago
AminBouchareb	07dda4056b	docs: document rune_missing_parentheses compiler error (#18589)	2 weeks 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 }, ...); } ``	2 weeks ago
Jared Dunham	f4918d86f3	docs: added generic type parameter example for $state (#18494)	2 weeks ago
Liam O'Dea	f5f70343df	perf: O(n²)→O(n) Map lookups for legacy reactive statements (#18602)	2 weeks 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.	2 weeks 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:	2 weeks 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>	2 weeks 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>	2 weeks ago
Scott Wu	5ccdfe3557	docs: note comments within tags possibility (#18482) ... Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks 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>	2 weeks 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>	2 weeks 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>	2 weeks 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).	2 weeks 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>	2 weeks 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.	2 weeks ago
Rudevin	388840b1b2	docs: note that transitions bypass CSS prefers-reduced-motion (#18597) ... --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks 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.	2 weeks 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>	2 weeks 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>	2 weeks 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)	2 weeks 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>	2 weeks 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>	2 weeks 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>	2 weeks 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 weeks 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 weeks 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>	2 weeks 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>	2 weeks ago
Yuichiro Yamashita	248a2e1db4	fix: transform expressions inside labeled statements during server compilation (#18617) ... close: #18615	2 weeks 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>	3 weeks 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>	3 weeks 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>	3 weeks ago