-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
Describe the bug
When we changed searchParams, and force to reload sveltekit data, url.searchParams remain the same value as before the change.
Reproduction
Reproduction:
https://stackblitz.com/edit/sveltejs-kit-template-default-xeika8?file=src%2Froutes%2F%2Bpage.svelte
click on the change url button. This will do a window.history.pushState with new searchParams then invalidate data, so it'll trigger the page.js load function.
In load function check url.searchParams (consol.log writes it).
The reproduction is a bit bad as this sandbox environment doesn't visibly change the url, but the reproduction is working locally or from any kind of hosting method.
This worked with SvelteKit 1.30.x. It is broken just after the SvelteKit 2.0 update. You can reproduce it with old and current SvelteKit.
Logs
No response
System Info
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
Memory: 6.48 GB / 15.93 GB
Binaries:
Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.7.5 - ~\AppData\Local\pnpm\pnpm.EXE
Browsers:
Edge: Chromium (120.0.2210.91)
Internet Explorer: 11.0.22621.1
Severity
critical
Additional Information
No response