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
Currently we rely on a hacky way of accessing certain SvelteKit event properties without triggering a route invalidation in our load wrappers.
SvelteKit 2 introduced the long discussed untrack function which should allow us to access the values in a safe and SvelteKit native way without triggering invalidation.
Since we want to maintain 1.x support, we need to implement this backwards-compatible and still rely on our hacky approach until we drop 1.x sometime in the future.
The text was updated successfully, but these errors were encountered:
Currently we rely on a hacky way of accessing certain SvelteKit event properties without triggering a route invalidation in our
load
wrappers.SvelteKit 2 introduced the long discussed
untrack
function which should allow us to access the values in a safe and SvelteKit native way without triggering invalidation.Since we want to maintain 1.x support, we need to implement this backwards-compatible and still rely on our hacky approach until we drop 1.x sometime in the future.
The text was updated successfully, but these errors were encountered: