Nick Sulkers

I came across something I believe is similar to this issue. I'm doing something like this: **App.svelte** ``` import DynamicTag from "./DynamicTag.svelte"; ``` **DynamicTag.svelte** ``` export let element = "div";...

The [TanStack docs](https://tanstack.com/query/latest/docs/framework/svelte/reactivity) have updated their examples, transitioning from `$:` statements to a combination of derived and writable stores. I'm not entirely pleased with this approach and have started relying...

Small sidenote: This issue doesn't appear to occur in earlier versions of svelte 5 (tested with 5.0.0-next.20).

I came across the same issue trying to debounce a value: ```svelte // debounce.svelte.ts export const debounce = (getValue: () => T, waitFor: number = 1000) => { let result...

To my knowledge, Tanstack Query has yet to support Svelte 5 runes, so directly feeding `$state` (assuming dependencyVariable is `$state`) won't yield the desired results. The Tanstack Query 5 documentation...

@SaintPepsi here's the function as I'm actually using it: **utils.svelte.ts** ```svelte export const reactiveQueryArgs = (cb: () => T) => { const store = writable(); $effect.pre(() => { store.set(cb()); });...

@frederikhors Your error is likely due to ```ts queryFn: getTeam(data!.teamId), ``` where getTeam (and specifically it's parameter) is executed immediately, before data contains a meaningful value. You probably intended to...