@remix-run/router 1.16.0-pre.1 → 1.16.1-pre.0

package/CHANGELOG.md

@@ -1,34 +1,26 @@
 # `@remix-run/router`
 
-## 1.16.0-pre.1
+## 1.16.1-pre.0
 
 ### Patch Changes
 
-- [REMOVE] Remove staticHandler.query flags that we can implement in dataStrategy ([#11384](https://github.com/remix-run/react-router/pull/11384))
+- Support `unstable_dataStrategy` on `staticHandler.queryRoute` ([#11515](https://github.com/remix-run/react-router/pull/11515))
 
-## 1.16.0-pre.0
+## 1.16.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
-
+- Move `unstable_dataStrategy` from `createStaticHandler` to `staticHandler.query` so it can be request-specific for use with the `ResponseStub` approach in Remix. It's not really applicable to `queryRoute` for now since that's a singular handler call anyway so any pre-processing/post/processing could be done there manually. ([#11377](https://github.com/remix-run/react-router/pull/11377))
 - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - Currently, active loaders revalidate after any action, regardless of the result
   - With this flag enabled, actions that return/throw a 4xx/5xx response status will no longer automatically revalidate
   - This should reduce load on your server since it's rare that a 4xx/5xx should actually mutate any data
   - If you need to revalidate after a 4xx/5xx result with this flag enabled, you can still do that via returning `true` from `shouldRevalidate`
   - `shouldRevalidate` now also receives a new `unstable_actionStatus` argument alongside `actionResult` so you can make decision based on the status of the `action` response without having to encode it into the action data
-
-- - Move `unstable_dataStrategy` from `createStaticHandler` to `staticHandler.query` so it can be request-specific for use with the `ResponseStub` approach in Remix. It's not really applicable to `queryRoute` for now since that's a singular handler call anyway so any pre-processing/post/processing could be done there manually. ([#11377](https://github.com/remix-run/react-router/pull/11377))
-  - Added a new `skipLoaders` flag to `staticHandler.query` for calling only the action in Remix Single Fetch
-- Added 2 new options to the `staticHandler.query` method for use in Remix's Single Fetch implementation: ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
-  - `loadRouteIds`: An optional array of route IDs to load if you wish to load a subset of the matched routes (useful for fine-grained revalidation)
-  - `skipLoaderErrorBubbling`: Disable error bubbling on loader executions for single-fetch scenarios where the client-side router will handle the bubbling
+- Added a `skipLoaderErrorBubbling` flag to `staticHandler.query` to disable error bubbling on loader executions for single-fetch scenarios where the client-side router will handle the bubbling ([#11098](https://github.com/remix-run/react-router/pull/11098))
 
 ## 1.15.3
 

package/dist/router.cjs.js

@@ -1,5 +1,5 @@
 /**
- * @remix-run/router v1.16.0-pre.1
+ * @remix-run/router v1.16.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *
@@ -3456,7 +3456,8 @@ function createStaticHandler(routes, opts) {
   async function queryRoute(request, _temp4) {
     let {
       routeId,
-      requestContext
+      requestContext,
+      unstable_dataStrategy
     } = _temp4 === void 0 ? {} : _temp4;
     let url = new URL(request.url);
     let method = request.method;
@@ -3485,7 +3486,7 @@ function createStaticHandler(routes, opts) {
         pathname: location.pathname
       });
     }
-    let result = await queryImpl(request, location, matches, requestContext, null, false, match);
+    let result = await queryImpl(request, location, matches, requestContext, unstable_dataStrategy || null, false, match);
     if (isResponse(result)) {
       return result;
     }