q-data.json: split per loader

.changeset/cuddly-bags-push.md

@@ -0,0 +1,5 @@
+---
+'@qwik.dev/router': minor
+---
+
+FIX: Route loaders now redirect in their JSON response instead of using HTTP redirect

.changeset/flat-hornets-fetch.md

@@ -0,0 +1,5 @@
+---
+'@qwik.dev/router': minor
+---
+
+FEAT: route loaders now accept `eTag` to shortcut data retrieval when the data has not changed. See the documentation for more details on this option and how to use it.

.changeset/fresh-loaders-update.md

@@ -0,0 +1,5 @@
+---
+'@qwik.dev/router': patch
+---
+
+fix(router): Update route loader metadata in the dev route trie when route source files change.

.changeset/green-experts-turn.md

@@ -0,0 +1,7 @@
+---
+'@qwik.dev/router': major
+---
+
+BREAKING: Route loaders are now AsyncSignals. This means that `value.failed` is no longer used to indicate a loader failure. Instead, if a loader fails, the error will be stored in `error`, and reading `value` will throw that error.
+
+This also means that you can now pass `expires`, `poll`, and `allowStale` options to route loaders. See the documentation for more details on these options and how to use them.

.changeset/loaders-no-action-state.md

@@ -0,0 +1,5 @@
+---
+'@qwik.dev/router': major
+---
+
+BREAKING: `routeLoader$` cannot read action state any more, so that they are cacheable and predictable. All use cases can be achieved in other ways, like reading the action signal directly in the component or having the loader read from URL-derived state that the action updates.

.changeset/nasty-pans-tickle.md

@@ -0,0 +1,13 @@
+---
+'@qwik.dev/router': major
+---
+
+BREAKING: Qwik Router no longer retrieves `q-data.json` files on every SPA navigation. You can remove any caching rules for these.
+
+Instead, Qwik Router now retrieves `q-loader-${hash}.${manifestHash}.json` for RouteLoader data. You can specify expiry for each RouteLoader individually, and it is automatically used to set browser caching headers. The `manifestHash` ensures that when you build a new version of your app, the old cached data will be invalidated and the new data will be fetched.
+
+The default expiry for RouteLoader data is 2 minutes, so that prefetching and caching of RouteLoader data is useful. You control this with the `expiry` option on each RouteLoader, and you can set it to `0` to disable caching.
+
+Furthermore, any RouteLoader that has `expiry: 0` will be generated as a file during SSG, which allows SPA navigation to work even without a server.
+
+Note: Be careful with caching for RouteLoaders that return user-specific data, especially regarding logout and CDN caching. Use low expiry times for these and use `eTag` to still allow caching benefits.

.changeset/warm-deer-take.md

@@ -0,0 +1,7 @@
+---
+'@qwik.dev/router': minor
+---
+
+FEAT: route loaders now accept `search` to only allow certain query parameters to trigger the loader. This means that random search parameters won't cause the loader to re-run. If you do not pass `search`, then all search parameters will be passed to the loader and will trigger it when they change.
+
+However, `qwikRouter` now has the option `strictLoaders` which is `true` by default, which means that if you do not specify `search` for a loader, then it will not receive any search parameters and will not re-run when the search parameters change.