Skip to content

Bubble or at least log Navigation Aborted Errors to Client #13778

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
elucidsoft opened this issue May 8, 2025 · 0 comments
Open

Bubble or at least log Navigation Aborted Errors to Client #13778

elucidsoft opened this issue May 8, 2025 · 0 comments

Comments

@elucidsoft
Copy link

Describe the bug

Navigation Aborted errors do not get bubbled up to the client, see my discussion here on what I went through to discover this.

#13777

Needless to say I would of save a great deal of time if it bubbled up the error message, as it took me an exceptionally long time to even realize it was a Navigation Aborted error in the first place. Then the number of things that can actually cause this problem are numerous and not well documented at all, the error it throws has absolutely zero information that is of any help when this happens as well. It's an exceptionally easy problem to get yourself into especially with reactive systems we build today, and an exceptionally hard problem to find with the way it's currently being treated.

Reproduction

Have a DOM event occur in the background while a navigation event occurs using goto, it will just sit there and do nothing. No error is thrown.

Logs

System Info

Svelte 4.x, SvelteKit 2.x 

(latest minors on all)

Severity

serious, but I can work around it

Additional Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant