@remix-run/router - npm Package Compare versions

Comparing version 1.16.0-pre.1 to 1.16.0

CHANGELOG.md

		# `@remix-run/router`

		## 1.16.0-pre.1
		## 1.16.0

		### Patch Changes

		- [REMOVE] Remove staticHandler.query flags that we can implement in dataStrategy ([#11384](https://github.com/remix-run/react-router/pull/11384))

		## 1.16.0-pre.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
		@@ -25,10 +17,4 @@ - With this flag enabled, actions that return/throw a 4xx/5xx response status will no longer automatically revalidate
		- `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
		- 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))

		- - 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

		## 1.15.3
		@@ -35,0 +21,0 @@

dist/router.umd.min.js

		/**
		* @remix-run/router v1.16.0-pre.1
		* @remix-run/router v1.16.0
		*
		@@ -4,0 +4,0 @@ * Copyright (c) Remix Software Inc.

package.json

		{
		"name": "@remix-run/router",
		"version": "1.16.0-pre.1",
		"version": "1.16.0",
		"description": "Nested/Data-driven/Framework-agnostic Routing",
		@@ -5,0 +5,0 @@ "keywords": [

dist/router.cjs.js

Sorry, the diff of this file is too big to display

dist/router.js

Sorry, the diff of this file is too big to display

dist/router.umd.js

Sorry, the diff of this file is too big to display

@remix-run/router - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics