Tee Ming

Please include a minimal reproduction instead of your entire project.

Thanks for posting your findings. I think it’s worth it to keep this open since it should still prerender correctly even with that preload strategy

Please provide a minimal reproduction in the form of a code repository.

Closing due to inactivity

I think this already works. I just tested it [here](https://stackblitz.com/edit/sveltejs-kit-template-default-tkjczf?description=The%20default%20SvelteKit%20template,%20generated%20with%20create-svelte&file=src%2Froutes%2Fabout%2F%2Blayout.server.js,src%2Froutes%2Fabout%2F%2Berror.svelte,src%2Froutes%2F%2Blayout.svelte,src%2Froutes%2Fabout%2Ftest%2F%2Bpage.svelte,src%2Froutes%2Fabout%2Ftest%2F%2Bpage.js,src%2Froutes%2Fabout%2F%2Bpage.js&title=SvelteKit%20Default%20Template). Can you provide an example to further explain your problem?

> @dummdidumm I don't use goto because of I don't want to navigate in real. I just want to change the url, and fetch some fresh data. Actually this is...

Possibly related changes [here](https://github.com/sveltejs/kit/pull/11307/files#diff-6bc786c5d82299b5eed36bb073cd7e3c8347af2951019da2b5dff1d5e3bad611) due to how `history.pushState` is being intercepted for shallow routing. Can you provide more information on how to reproduce or how to setup Google Analytics to...

You really don't get anything useful from logging url.searchParams. The output will be `URLSearchParams {}` on the server. However, this is still a bug since kit shouldn't crash from this.

Please provide a minimal reproduction in the form of a code repository.

Please provide a minimal reproduction in the form of a code repository that produces this issue.