From kit@2.60.0 there is a problem with `afterNavigate` and queryparams

[frederikhors]

I do not have time now to create a reproduction but the problem is real! I'll update this post soon.

[thorbm1500]

I too am currently experiencing issues with afterNavigate.
I am unsure what your issue is, but, I have one certain page where afterNavigate is not called when the page is refreshed, but is called if the page is navigated to from another page within the project. This only happens for me on this specific page, and I think it might be an issue with having too big of a workload on the initial load, tho would of course prefer that not to be an issue.

The page in question for me is github/thorbm1500/argxs/.../+page.svelte

I'll of course create a new issue, if this is unrelated to your situation.

[frederikhors]

@thorbm1500 maybe is the same. I'm really short on time these days unfortunately!

[Nic-Polumeyv]

The only navigation-lifecycle change in 2.60.0 is #15811. Since that release, a navigation that gets superseded while the new page is rendering aborts before its afterNavigate callbacks run, and an awaited goto rejects with "navigation aborted". Rapid query-param goto calls hit that window, and so does calling invalidate or invalidateAll while a navigation is in flight. The invalidate case was removed in v3 by #16188, which is breaking and won't land in v2. Does that match what you're seeing? If not, this still needs a repro.

@thorbm1500 afterNavigate also runs when the component first mounts, so not firing on a plain refresh is a different problem than this one and worth its own issue with a repro.

[frederikhors]

I fixed the issue using LLMs. I haven't explored the issue in detail. We can close if you like.

[Nic-Polumeyv]

Just trying to help maintainers by doing some issue cleanup. If you can state what you learned or what the issue was here that would be the best way to close it out. Or just close it

[frederikhors]

I don't know what the problem was. I'm closing for now.