Data loader uses old route params, when navigation changes to to fast.

[minht11]

Data loader uses old route params, when navigation changes to to fast.

Reproduction

1. Go to example https://stackblitz.com/edit/vitejs-vite-xntgcq
2. Click on link "Test 2" few times, then quickly click on link "Test 1"
3. Observe that params from current route, and data loader mismatch.

Screen.Recording.2023-07-15.at.23.30.01.mov

[posva]

This might be related to #201. I think it's a mix of the current cached behavior and not properly discarding old fetching. I think adding different stages to the data, e.g. waiting for all of the loaders to be resolved before applying will help for this and #201

[posva]

@minht11 Some heads-up: this and other bugs are fixed but the next release will likely be a major that replaces the current implementation of defineLoader. I haven't written the changelog yet and I do hope to add deprecations in the meantime but the new fixed version does not have a cache (yet) and things like invalidate, pendingLoad, and cacheTime do not exist anymore. Ideally, I will create another define loader for cache that uses a light lru cache but I think the priority should be having a loader with no cache (since most of GET cache should be handled at server level anyway) and move from there to support other patterns and update vuejs/rfcs#460