You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request (#10479)
When using Lazy Route Discovery (future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)
On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
On fetcher calls to undiscovered routes, this mismatch will trigger a document reload of the current path
While performing Eager Route Discovery on rendered <Link> components, mismatches will result in a no-op
Single Fetch: fix revalidation behavior bugs (#9938)
With Single Fetch, existing routes revalidate by default
This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
There are two conditions that will trigger granular revalidation:
If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a
Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)
Reverts the logic originally added in Remix v1.18.0 via #6409
This was added to resolve an issue that could arise when doing quick back/forward history navigations while JS was loading which would cause a mismatch between the server matches and client matches: #1757
This specific hydration issue would then cause this React v17 only looping issue: #1678
The URL comparison that we added in 1.18.0 turned out to be subject to false positives of it's own which could also put the user in looping scenarios
Remix v2 upgraded it's minimal React version to v18 which eliminated the v17 hydration error loop
React v18 handles this hydration error like any other error and does not result in a loop
So we can remove our check and thus avoid the false-positive scenarios in which it may also trigger a loop
Fog of War: Simplify implementation now that React Router handles slug/splat edge cases and tracks previously discovered routes (see remix-run/react-router#11883) (#9860)
This changes the return signature of the internal __manifest endpoint since we no longer need the notFoundPaths field
Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)
Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)
Single Fetch: Remove responseStub in favor of headers (#9769)
Background
The original Single Fetch approach was based on an assumption that an eventual middleware implementation would require something like ResponseStub so users could mutate status/headers in middleware before/after handlers as well as during handlers
We wanted to align how headers got merged between document and data requests
So we made document requests also use ResponseStub and removed the usage of headers in Single Fetch
The realization/alignment between Michael and Ryan on the recent roadmap planning made us realize that the original assumption was incorrect
middleware won't need a stub - users can just mutate the Response they get from await next() directly
With that gone, and still wanting to align how headers get merged, it makes more sense to stick with the current headers API and apply that to Single Fetch and avoid introducing a totally new thing in RepsonseStub (that always felt a bit awkward to work with anyway)
With this change:
You are encouraged to stop returning Response instances in favor of returning raw data from loaders and actions:
~~return json({ data: whatever });~~
return { data: whatever };
In most cases, you can remove your json() and defer() calls in favor of returning raw data if they weren't setting custom status/headers
We will be removing both json and defer in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behavior
If you need custom status/headers:
We've added a new unstable_data({...}, responseInit) utility that will let you send back status/headers alongside your raw data without having to encode it into a Response
The headers() function will let you control header merging for both document and data requests
Patch Changes
Single Fetch: Ensure calls don't include any trailing slash from the pathname (i.e., /path/.data) (#9792)
Single Fetch: Add undefined to the useRouteLoaderData type override (#9796)
Change initial hydration route mismatch from a URL check to a matches check to be resistant to URL inconsistencies (#9695)
Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
You can return naked objects with Promise's without needing to use defer() - including nested Promise's
If you need to return a custom status code or custom response headers, you can still use the defer utility
<RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate
Allow an optional Layout export from the root route (#8709)
Vite: Add a new basename option to the Vite plugin, allowing users to set the internal React Router basename in order to to serve their applications underneath a subpath (#8145)
Patch Changes
Fix a bug with SPA mode when the root route had no children (#8747)
Add support for clientLoader/clientAction/HydrateFallback route exports (RFC). (#8173)
Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:
Leveraging a data source local to the browser (i.e., localStorage)
Managing a client-side cache of server data (like IndexedDB)
Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
Migrating a React Router SPA to a Remix application
By default, clientLoader will not run on hydration, and will only run on subsequent client side navigations.
If you wish to run your client loader on hydration, you can set clientLoader.hydrate=true to force Remix to execute it on initial page load. Keep in mind that Remix will still SSR your route component so you should ensure that there is no new required data being added by your clientLoader.
If your clientLoader needs to run on hydration and adds data you require to render the route component, you can export a HydrateFallback component that will render during SSR, and then your route component will not render until the clientLoader has executed on hydration.
clientAction is simpler than clientLoader because it has no hydration use-cases. clientAction will only run on client-side navigations.
Add a new future.v3_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. For more information, please see the React Router 6.21.0 Release Notes and the useResolvedPath docs. (#8216)
Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#7882)
Patch Changes
Support rendering of LiveReload component after Scripts in Vite dev (#7919)
Support optional rendering of LiveReload component in Vite dev (#7919)
add missing modulepreload for the manifest (#7684)
Unstable Vite support for Node-based Remix apps (#7590)
remix build 👉 vite build && vite build --ssr
remix dev 👉 vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
See "Future > Vite" in the Remix Docs for details
Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmounted in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)
Fix warning that could be logged when using route files with no default export (#7745)
It seems our compiler compiles these files to export an empty object as the default which we can then end up passing to React.createElement, triggering the console warning, but generally no UI issues
By properly detecting these, we can correctly pass Component: undefined off to the React Router layer
This is technically an potential issue in the compiler but it's an easy patch in the @remix-run/react layer and hopefully disappears in a Vite world
Fix critical CSS hydration errors for Vite dev (#7812)
Add experimental support for the View Transitions API via document.startViewTransition to enable CSS animated transitions on SPA navigations in your application (#7648)
Avoid mutating meta object when tagName is specified (#7594)
Fix FOUC on subsequent client-side navigations to route.lazy routes (#7576)
Emulate types for JSON.parse(JSON.stringify(x)) in SerializeFrom (#7605)
Notably, type fields that are only assignable to undefined after serialization are now omitted since JSON.stringify |> JSON.parse will omit them -- see test cases for examples
Also fixes type errors when upgrading to v2 from 1.19
Export the proper Remix useMatches wrapper to fix UIMatch typings (#7551)
When using Lazy Route Discovery (future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)
On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
On fetcher calls to undiscovered routes, this mismatch will trigger a document reload of the current path
While performing Eager Route Discovery on rendered <Link> components, mismatches will result in a no-op
Fix single-fetch types when loader, action, clientLoader, or clientAction return a mixture of bare objects, json(...), defer(...), and unstable_data(...). (#9999)
Single Fetch: Re-export interface Future through @remix-run/node/@remix-run/cloudflare/@remix-run/deno packages so that pnpm doesn't complain about @remix-run/server-runtime not being a dependency (#9982)
Single Fetch: Do not try to encode a turbo-stream body into 304 responses (#9941)
Single Fetch: fix revalidation behavior bugs (#9938)
With Single Fetch, existing routes revalidate by default
This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
There are two conditions that will trigger granular revalidation:
If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a
Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)
Reverts the logic originally added in Remix v1.18.0 via #6409
This was added to resolve an issue that could arise when doing quick back/forward history navigations while JS was loading which would cause a mismatch between the server matches and client matches: #1757
This specific hydration issue would then cause this React v17 only looping issue: #1678
The URL comparison that we added in 1.18.0 turned out to be subject to false positives of it's own which could also put the user in looping scenarios
Remix v2 upgraded it's minimal React version to v18 which eliminated the v17 hydration error loop
React v18 handles this hydration error like any other error and does not result in a loop
So we can remove our check and thus avoid the false-positive scenarios in which it may also trigger a loop
Single Fetch: Fix redirects when a basename is present (#9848)
Fog of War: Simplify implementation now that React Router handles slug/splat edge cases and tracks previously discovered routes (see remix-run/react-router#11883) (#9860)
This changes the return signature of the internal __manifest endpoint since we no longer need the notFoundPaths field
Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)
Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)
Single Fetch: Remove responseStub in favor of headers (#9769)
Background
The original Single Fetch approach was based on an assumption that an eventual middleware implementation would require something like ResponseStub so users could mutate status/headers in middleware before/after handlers as well as during handlers
We wanted to align how headers got merged between document and data requests
So we made document requests also use ResponseStub and removed the usage of headers in Single Fetch
The realization/alignment between Michael and Ryan on the recent roadmap planning made us realize that the original assumption was incorrect
middleware won't need a stub - users can just mutate the Response they get from await next() directly
With that gone, and still wanting to align how headers get merged, it makes more sense to stick with the current headers API and apply that to Single Fetch and avoid introducing a totally new thing in RepsonseStub (that always felt a bit awkward to work with anyway)
With this change:
You are encouraged to stop returning Response instances in favor of returning raw data from loaders and actions:
~~return json({ data: whatever });~~
return { data: whatever };
In most cases, you can remove your json() and defer() calls in favor of returning raw data if they weren't setting custom status/headers
We will be removing both json and defer in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behavior
If you need custom status/headers:
We've added a new unstable_data({...}, responseInit) utility that will let you send back status/headers alongside your raw data without having to encode it into a Response
The headers() function will let you control header merging for both document and data requests
Patch Changes
Change initial hydration route mismatch from a URL check to a matches check to be resistant to URL inconsistencies (#9695)
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
This PR contains the following updates:
^2.0.0->^2.16.5^2.0.0->^2.16.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
remix-run/remix (@remix-run/react)
v2.16.5Compare Source
Patch Changes
@remix-run/[email protected]v2.16.4Compare Source
Patch Changes
@remix-run/[email protected]v2.16.3Compare Source
Patch Changes
@remix-run/[email protected]v2.16.2Compare Source
Patch Changes
shouldRevalidatebehavior forclientLoader-only routes inssr:trueapps (#10527)@remix-run/[email protected]v2.16.1Compare Source
Patch Changes
@remix-run/reactfailing when the package is not marked as external (#10528)@remix-run/[email protected]v2.16.0Compare Source
Patch Changes
Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request (#10479)
When using Lazy Route Discovery (
future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)fetchercalls to undiscovered routes, this mismatch will trigger a document reload of the current path<Link>components, mismatches will result in a no-opUpdated dependencies:
@remix-run/[email protected]v2.15.3Compare Source
Patch Changes
@remix-run/[email protected]v2.15.2Compare Source
Patch Changes
@remix-run/[email protected]v2.15.1Compare Source
Patch Changes
@remix-run/[email protected]v2.15.0Compare Source
Patch Changes
@remix-run/[email protected]v2.14.0Compare Source
Patch Changes
defaultShouldRevalidatevalue when using single fetch (#10139)@remix-run/[email protected]v2.13.1Compare Source
Patch Changes
@remix-run/[email protected]v2.13.0Compare Source
Minor Changes
unstable_dataStrategy->dataStrategyunstable_patchRoutesOnNavigation->patchRoutesOnNavigationunstable_data()->data()unstable_viewTransition->viewTransition(Link,Form,navigate,submit)unstable_flushSync>-><Link viewTransition>(Link,Form,navigate,submit,useFetcher)future.unstable_singleFetch->future.v3_singleFetchfuture.unstable_lazyRouteDiscovery->future.v3_lazyRouteDiscoveryPatch Changes
clientLoader.hydratein a layout route when hydrating with bubbled errors (#10063)@remix-run/[email protected]v2.12.1Compare Source
Patch Changes
@remix-run/[email protected]v2.12.0Compare Source
Patch Changes
Lazy Route Discovery: Sort
/__manifestquery parameters for better caching (#9888)Single Fetch: fix revalidation behavior bugs (#9938)
GET /a/b/c.datashouldRevalidate, it will be excluded from the single fetch callclientLoaderthen it will be excluded from the single fetch call and if you callserverLoader()from yourclientLoader, that will make a separarte HTTP call for just that route loader - i.e.,GET /a/b/c.data?_routes=routes/afor aclientLoaderinroutes/a.tsxrootroute androutes/bhad aloaderbutroutes/cdid not, the single fetch request would beGET /a/b/c.data?_routes=root,routes/aRemove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)
v1.18.0via #64091.18.0turned out to be subject to false positives of it's own which could also put the user in looping scenariosSingle Fetch: Improved typesafety (#9893)
If you were already using previously released unstable single-fetch types:
"@​remix-run/react/future/single-fetch.d.ts"override fromtsconfig.json>compilerOptions>typesdefineLoader,defineAction,defineClientLoader,defineClientActionhelpers from your route modulesUIMatch_SingleFetchtype helper withUIMatchMetaArgs_SingleFetchtype helper withMetaArgsThen you are ready for the new typesafety setup:
For more information, see Guides > Single Fetch in our docs.
Clarify wording in default
HydrateFallbackconsole warning (#9899)Updated dependencies:
@remix-run/[email protected]v2.11.2Compare Source
Patch Changes
__manifestendpoint since we no longer need thenotFoundPathsfieldunstable_patchRoutesOnNavigationfunction in RR (see remix-run/react-router#11888) (#9860)turbo-streamtov2.3.0(#9856)@remix-run/[email protected]v2.11.1Compare Source
Patch Changes
a7cffe57)@remix-run/[email protected]v2.11.0Compare Source
Minor Changes
Single Fetch: Add a new
unstable_data()API as a replacement forjson/deferwhen customstatus/headersare needed (#9769)Add a new
replace(url, init?)alternative toredirect(url, init?)that performs ahistory.replaceStateinstead of ahistory.pushStateon client-side navigation redirects (#9764)Rename
future.unstable_fogOfWartofuture.unstable_lazyRouteDiscoveryfor clarity (#9763)Single Fetch: Remove
responseStubin favor ofheaders(#9769)Background
middlewareimplementation would require something likeResponseStubso users could mutatestatus/headersinmiddlewarebefore/after handlers as well as during handlersheadersgot merged between document and data requestsResponseStuband removed the usage ofheadersin Single Fetchmiddlewarewon't need a stub - users can just mutate theResponsethey get fromawait next()directlyheadersget merged, it makes more sense to stick with the currentheadersAPI and apply that to Single Fetch and avoid introducing a totally new thing inRepsonseStub(that always felt a bit awkward to work with anyway)With this change:
Responseinstances in favor of returning raw data from loaders and actions:return json({ data: whatever });~~return { data: whatever };json()anddefer()calls in favor of returning raw data if they weren't setting customstatus/headersjsonanddeferin the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behaviorstatus/headers:unstable_data({...}, responseInit)utility that will let you send backstatus/headersalongside your raw data without having to encode it into aResponseheaders()function will let you control header merging for both document and data requestsPatch Changes
/path/.data) (#9792)undefinedto theuseRouteLoaderDatatype override (#9796)@remix-run/[email protected]v2.10.3Compare Source
Patch Changes
request.signalthroughdataStrategyforloadercalls to fix cancellation (#9738)future.v7_skipActionErrorRevalidationunder the hood (#9706)shouldRevalidateparameter fromunstable_actionStatustoactionStatus@remix-run/[email protected]v2.10.2Compare Source
Patch Changes
reftoForm(bdd04217)@remix-run/[email protected]v2.10.1Compare Source
Patch Changes
reloadDocument(#9686)<Form>components (#9665)@remix-run/[email protected]v2.10.0Compare Source
Minor Changes
Add support for Lazy Route Discovery (a.k.a. Fog of War) (#9600)
Patch Changes
loaderdata whenclientLoaderexists (#9580)LayoutErrorBoundaryrenders also throw (#9566)basename(#9584)[email protected]for single fetch (#9562)@remix-run/[email protected]v2.9.2Compare Source
Patch Changes
undefinedtouseActionDatatype override (#9322)nonceto be set on single fetch stream transfer inline scripts (#9364)defineLoader,defineClientLoader,defineAction,defineClientAction(#9372, #9404)@remix-run/[email protected]v2.9.1Compare Source
Patch Changes
future/*.d.tsfiles from TS build (#9299)@remix-run/[email protected]v2.9.0Compare Source
Minor Changes
New
future.unstable_singleFetchflag (#8773)turbo-streamsoDate's will becomeDatethroughuseLoaderData()Promise's without needing to usedefer()- including nestedPromise'sdeferutility<RemixServer abortDelay>is no longer used. Instead, you shouldexport const streamTimeoutfromentry.server.tsxand the remix server runtime will use that as the delay to abort the streamed responserenderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed downfuture.unstable_skipActionErrorRevalidationflag) - you can return a 2xx to opt-into revalidation or useshouldRevalidateOpt-in types for single-fetch (#9272)
./node_modules/@​remix-run/react/future/single-fetch.d.tstoincludein yourtsconfig.jsonPatch Changes
@remix-run/[email protected]v2.8.1Compare Source
Patch Changes
LayoutComponenttype to accept limited children (#8910)@remix-run/[email protected]v2.8.0Compare Source
Patch Changes
ErrorBoundarycomponent so it leverages the user-providedLayoutcomponent (#8859)HydrateFallbackcomponent so it leverages any user-providedLayoutcomponent (#8892)@remix-run/reactre-exports everything fromreact-router-domfor SPA mode (#8929)@remix-run/[email protected]v2.7.2Compare Source
Patch Changes
@remix-run/[email protected]v2.7.1Compare Source
Patch Changes
@remix-run/[email protected]v2.7.0Compare Source
Minor Changes
Layoutexport from the root route (#8709)basenameoption to the Vite plugin, allowing users to set the internal React Routerbasenamein order to to serve their applications underneath a subpath (#8145)Patch Changes
@remix-run/[email protected]v2.6.0Compare Source
Patch Changes
@remix-run/[email protected]v2.5.1Compare Source
Patch Changes
<Meta>/<Links>in SPA mode (#8538)unstable_prefix fromBlocker/BlockerFunctiontypes (#8530)@remix-run/[email protected]v2.5.0Compare Source
Minor Changes
Add unstable support for "SPA Mode" (#8457)
You can opt into SPA Mode by setting
unstable_ssr: falsein your Remix Vite plugin config:Development in SPA Mode is just like a normal Remix app, and still uses the Remix dev server for HMR/HDR:
Building in SPA Mode will generate an
index.htmlfile in your client assets directory:To run your SPA, you serve your client assets directory via an HTTP server:
For more information, please refer to the SPA Mode docs.
Patch Changes
import.meta.hotfrom the existing Remix compiler (#8459)@remix-run/[email protected]v2.4.1Compare Source
Patch Changes
loadererrors throughserverLoaderin hydratingclientLoader's (#8304)Responsehelpers (defer/json/redirect/redirectDocument) through@remix-run/reactfor use inclientLoader/clientAction(#8351)@remix-run/[email protected]v2.4.0Compare Source
Minor Changes
Add support for
clientLoader/clientAction/HydrateFallbackroute exports (RFC). (#8173)Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:
localStorage)IndexedDB)By default,
clientLoaderwill not run on hydration, and will only run on subsequent client side navigations.If you wish to run your client loader on hydration, you can set
clientLoader.hydrate=trueto force Remix to execute it on initial page load. Keep in mind that Remix will still SSR your route component so you should ensure that there is no new required data being added by yourclientLoader.If your
clientLoaderneeds to run on hydration and adds data you require to render the route component, you can export aHydrateFallbackcomponent that will render during SSR, and then your route component will not render until theclientLoaderhas executed on hydration.clientActionis simpler thanclientLoaderbecause it has no hydration use-cases.clientActionwill only run on client-side navigations.For more information, please refer to the
clientLoaderandclientActiondocumentation.Add a new
future.v3_relativeSplatPathflag to implement a breaking bug fix to relative routing when inside a splat route. For more information, please see the React Router6.21.0Release Notes and theuseResolvedPathdocs. (#8216)Patch Changes
@remix-run/[email protected]v2.3.1Compare Source
Patch Changes
@remix-run/[email protected]v2.3.0Compare Source
Minor Changes
unstable_prefix from theuseBlockerhook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix fromunstable_usePromptdue to differences in how browsers handlewindow.confirmthat prevent React Router from guaranteeing consistent/correct behavior. (#7882)Patch Changes
LiveReloadcomponent afterScriptsin Vite dev (#7919)LiveReloadcomponent in Vite dev (#7919)[email protected]@remix-run/[email protected]@remix-run/[email protected]v2.2.0Compare Source
Minor Changes
remix build👉vite build && vite build --ssrremix dev👉vite devfuture.v3_fetcherPersistflag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmounted in the UI, fetchers will persist until they return to anidlestate (RFC) (#7704)Patch Changes
defaultexport (#7745)defaultwhich we can then end up passing toReact.createElement, triggering the console warning, but generally no UI issuesComponent: undefinedoff to the React Router layer@remix-run/reactlayer and hopefully disappears in a Vite world@remix-run/[email protected][email protected]@remix-run/[email protected]v2.1.0Compare Source
Minor Changes
document.startViewTransitionto enable CSS animated transitions on SPA navigations in your application (#7648)Patch Changes
metaobject whentagNameis specified (#7594)route.lazyroutes (#7576)JSON.parse(JSON.stringify(x))inSerializeFrom(#7605)undefinedafter serialization are now omitted sinceJSON.stringify |> JSON.parsewill omit them -- see test cases for examplesuseMatcheswrapper to fixUIMatchtypings (#7551)@remix-run/[email protected][email protected]@remix-run/[email protected]v2.0.1Compare Source
Patch Changes
UIMatchforhandlefield (#7464)route.lazy(#7498)ErrorResponseinstead of just anErrorwhen submitting to a route without anaction(#7423)@remix-run/[email protected]remix-run/remix (@remix-run/server-runtime)
v2.16.5Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.16.5.v2.16.4Compare Source
Patch Changes
cookiedependency from^0.6.0 -> ^0.7.2to fix security advisory (#10547)v2.16.3Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.16.3.v2.16.2Compare Source
Patch Changes
v2.16.1Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.16.1.v2.16.0Compare Source
Patch Changes
When using Lazy Route Discovery (
future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)fetchercalls to undiscovered routes, this mismatch will trigger a document reload of the current path<Link>components, mismatches will result in a no-opv2.15.3Compare Source
Patch Changes
Set-Cookieheaders could be duplicated if also returned fromheaders(#10424)v2.15.2Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.15.2.v2.15.1Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.15.1.v2.15.0Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.15.0.v2.14.0Compare Source
Minor Changes
SerializeFromin favor of generics because it will be removed in React Router v7 (#10173)Patch Changes
v2.13.1Compare Source
No significant changes to this package were made in this release. See the repo
CHANGELOG.mdfor an overview of all changes in v2.13.1.v2.13.0Compare Source
Minor Changes
unstable_dataStrategy->dataStrategyunstable_patchRoutesOnNavigation->patchRoutesOnNavigationunstable_data()->data()unstable_viewTransition->viewTransition(Link,Form,navigate,submit)unstable_flushSync>-><Link viewTransition>(Link,Form,navigate,submit,useFetcher)future.unstable_singleFetch->future.v3_singleFetchfuture.unstable_lazyRouteDiscovery->future.v3_lazyRouteDiscoveryv2.12.1Compare Source
Patch Changes
loader,action,clientLoader, orclientActionreturn a mixture of bare objects,json(...),defer(...), andunstable_data(...). (#9999)interface Futurethrough@remix-run/node/@remix-run/cloudflare/@remix-run/denopackages so thatpnpmdoesn't complain about@remix-run/server-runtimenot being a dependency (#9982)v2.12.0Compare Source
Patch Changes
Single Fetch: Do not try to encode a
turbo-streambody into 304 responses (#9941)Single Fetch: fix revalidation behavior bugs (#9938)
GET /a/b/c.datashouldRevalidate, it will be excluded from the single fetch callclientLoaderthen it will be excluded from the single fetch call and if you callserverLoader()from yourclientLoader, that will make a separarte HTTP call for just that route loader - i.e.,GET /a/b/c.data?_routes=routes/afor aclientLoaderinroutes/a.tsxrootroute androutes/bhad aloaderbutroutes/cdid not, the single fetch request would beGET /a/b/c.data?_routes=root,routes/aRemove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)
v1.18.0via #64091.18.0turned out to be subject to false positives of it's own which could also put the user in looping scenariosSingle Fetch: Improved typesafety (#9893)
If you were already using previously released unstable single-fetch types:
"@​remix-run/react/future/single-fetch.d.ts"override fromtsconfig.json>compilerOptions>typesdefineLoader,defineAction,defineClientLoader,defineClientActionhelpers from your route modulesUIMatch_SingleFetchtype helper withUIMatchMetaArgs_SingleFetchtype helper withMetaArgsThen you are ready for the new typesafety setup:
For more information, see Guides > Single Fetch in our docs.
Single Fetch: Change content type on
.datarequests totext/x-scriptto allow Cloudflare compression (#9889)Support 304 responses on document requests (#9955)
v2.11.2Compare Source
Patch Changes
basenameis present (#9848)__manifestendpoint since we no longer need thenotFoundPathsfieldunstable_patchRoutesOnNavigationfunction in RR (see remix-run/react-router#11888) (#9860)turbo-streamtov2.3.0(#9856)v2.11.1Compare Source
Patch Changes
a7cffe57)v2.11.0Compare Source
Minor Changes
Single Fetch: Add a new
unstable_data()API as a replacement forjson/deferwhen customstatus/headersare needed (#9769)Add a new
replace(url, init?)alternative toredirect(url, init?)that performs ahistory.replaceStateinstead of ahistory.pushStateon client-side navigation redirects (#9764)Rename
future.unstable_fogOfWartofuture.unstable_lazyRouteDiscoveryfor clarity (#9763)Single Fetch: Remove
responseStubin favor ofheaders(#9769)Background
middlewareimplementation would require something likeResponseStubso users could mutatestatus/headersinmiddlewarebefore/after handlers as well as during handlersheadersgot merged between document and data requestsResponseStuband removed the usage ofheadersin Single Fetchmiddlewarewon't need a stub - users can just mutate theResponsethey get fromawait next()directlyheadersget merged, it makes more sense to stick with the currentheadersAPI and apply that to Single Fetch and avoid introducing a totally new thing inRepsonseStub(that always felt a bit awkward to work with anyway)With this change:
Responseinstances in favor of returning raw data from loaders and actions:return json({ data: whatever });~~return { data: whatever };json()anddefer()calls in favor of returning raw data if they weren't setting customstatus/headersjsonanddeferin the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behaviorstatus/headers:unstable_data({...}, responseInit)utility that will let you send backstatus/headersalongside your raw data without having to encode it into aResponseheaders()function will let you control header merging for both document and data requestsPatch Changes
v2.10.3Compare Source
No significant changes to this package were made in this release. [See the repo
CHANGELOG.md](https://redirect.github.comConfiguration
📅 Schedule: Branch creation - "before 7am on the first day of the week" in timezone GMT, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.