Umami breaks client side navigation with auto-tracking

[HighPriest]

Hi.

I have found out that the automatic Umami page view tracker is breaking client side navigation, by forcing full page reloads whenever the url changes. This happens when navigation is done both with anchor tags & with goTo function

I am trying out this tool in response to relevant Issue on Umami board Nr.3267.

Unfortunately, I see that this package does not introduce custom handler for automatic page tracking, thus falling prey to the same issue which is plaguing the umami tracker when it is loaded from HTML <script> tag.

[SaschaLucius]

Hi,
@HighPriest you are right, I'm just wrapping the Umami script right now,
specially to avoid adopting the package each time when Umami changes and not run into CORS issues in the frontend.
I have done a prototype in the past, to re-write a client for Umami, but stopped on it because it felt not beneficial at all.

So currently, I have nothing in mind how I could help you with your specific problem.

Are you asking with this open issue for a specific adoption or feature request?

[HighPriest]

Primarily, I am posting these Issues, to raise awareness about Umamis "hijack navigation, send tracking message, return navigation" approach breaking client side navigation functionality.

It took me a while to figure out that the cause was Umami after adding it to an advanced project. In dev env & on a fast connection, it has not been immediately obvious that client side navigation no longer works.

Secondarily, it is a good starting point to discuss a way to hook umami script to sveltes navigation, so we can have tracking work as it should.