invalidate resource

[tanhauhau]

Fixes #1277

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

[Conduitry]

I haven't looked at this too closely and I haven't tried it out, but I think it would probably be good to normalize the URLs that are saved during each load() and that are passed to invalidate().

[benmccann]

looks like tabs got converted to spaces in this file

[Rich-Harris]

working on this locally — at the moment it doesn't play well with caching (if you invalidate a URL within a page's maxage window, it doesn't do anything). am also wondering if we should batch invalidations, or if invalidate(...urls) is a sufficiently good API that batching is unnecessary

[Conduitry]

Scheduled-for-next-microtask batching, like a bunch of other things in Svelte core, might be nice. Were you thinking of larger batches than that?

[Rich-Harris]

no, just microtask

[Rich-Harris]

closing in favour of #1303 — thanks