Is there a way to create window.location.replace in SvelteKit, like we can use goto()?

I want a way to not save the current URL in history. The current URL has query strings that change and the user cannot use the back button to go to the previous page. Instead, just go to the page with different query strings.

Edit: I am using history.pushState() and history.replaceState() to not save the URLs in history. I wish there was a built-in way in SvelteKit to do this.

Is there a way to create window.location.replace in SvelteKit, like we can use goto()?

I want a way to not save the current URL in history. The current URL has query strings that change and the user cannot use the back button to go to the previous page. Instead, just go to the page with different query strings.

Edit: I am using history.pushState() and history.replaceState() to not save the URLs in history. I wish there was a built-in way in SvelteKit to do this.

• javascript
• svelte
• browser-history
• sveltekit

Share Improve this question Follow edited Oct 10, 2022 at 3:26 Michael M. 11.1k1111 gold badges2121 silver badges4444 bronze badges asked Oct 9, 2022 at 18:45 da-navda-nav 5111 silver badge33 bronze badges 3

• What exactly is the problem? replace does not navigate, so why not just use it? – brunnerh Commented Oct 9, 2022 at 19:18
• replace pletely reloads the page making a few ponents useless. – da-nav Commented Oct 10, 2022 at 3:25
• Sorry, what I meant was history.replaceState. There is no need for SvelteKit to have anything like that because it should not interact with its routing. – brunnerh Commented Oct 10, 2022 at 5:09

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 6

There is a replaceState parameter on goto that may do what you're looking for.

goto('/wherever', { replaceState: true });

Looks like the options passed to goto could be better documented, I'll see if I can fix that.

Current docs