[breaking] only route pages on the client-side

[benmccann]

Right now we have to send a list of all endpoints to the client, but 99% of the time they aren't used for anything and so it's generally unnecessary bandwidth overhead.

Removing this means that developers need to put rel="external" on any link to an endpoint. This seems like a reasonable trade-off since it is very rare to link to endpoints. Endpoints are primarily gotten via fetch which doesn't utilize the router.

In addition to reducing the size of the client JS, it also will make it slightly easier to refactor out the router (#2611) since it will have one less concern to deal with

[changeset-bot]

🦋 Changeset detected

Latest commit: efd5fb7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Conduitry]

Discussions about sveltekit:external aside, I do think this is probably a reasonable change to make to how routing is handled if it means less stuff getting sent to the client. Rich should probably weigh in, though, and if we're going to be making this change, we should make sure the docs are updated to make the new behavior clear.

[benmccann]

Asked Rich about this on Discord:

snuck a look — i think the rel=external thing is a reasonable tradeoff

[bekos]

@benmccann Is there an equivalent option when using goto instead of href?

[benmccann]

you could just do document.location.href = newUrl; instead of using goto

[bekos]

thx for the tip @benmccann 👍 the only issue is that I lost the $navigating changes and it's loading animation in this case 🤷but I can live with that 😃

[benquan]

This reasoning is completely ommited from the documentation. This post is the only reference I have found to do this. The client side error doesn't help either: