From 3df2645451e6e9441e02d423d2fe77b8e4a38f59 Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Fri, 6 Mar 2026 11:27:47 -0500 Subject: [PATCH] chore: deactivate batch after async derived resolves (#17865) Extracted from #17805. Similar to #17864, I'm not aware of any bugs resulting from this, but the fact that we're setting `current_batch` before calling `internal_set` and then not _unsetting_ `current_batch` feels like something that could potentially bite us. --- packages/svelte/src/internal/client/reactivity/deriveds.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/svelte/src/internal/client/reactivity/deriveds.js b/packages/svelte/src/internal/client/reactivity/deriveds.js index 7df7651294..c1ee4f3f52 100644 --- a/packages/svelte/src/internal/client/reactivity/deriveds.js +++ b/packages/svelte/src/internal/client/reactivity/deriveds.js @@ -196,6 +196,8 @@ export function async_derived(fn, label, location) { if (decrement_pending) { decrement_pending(); } + + batch.deactivate(); }; d.promise.then(handler, (e) => handler(null, e || 'unknown'));