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.
Currently we rely on a hacky way of accessing certain SvelteKit event properties without triggering a route invalidation in our
loadwrappers.SvelteKit 2 introduced the long discussed
untrackfunction 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.