Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

# custom server (Express example)
npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in `@remix-run/dev`

unstable_vitePlugin: The new Remix Vite plugin
unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

Deno support is untested, but should work through Deno's Node/npm interop
CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
- <Form method="post" navigate={false} fetcherKey="my-key">
- submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })
- Invoking a fetcher in this way is ephemeral and stateless
- If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

Persistence Future Flag (`future.v3_fetcherPersist`)

Per the same RFC as above, we've introduced a new future.v3_fetcherPersist flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an idle state. This makes pending/optimistic UI much easier in scenarios where the originating fetcher needs to unmount. (#10962)

This is sort of a long-standing bug fix as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
- Fetchers that complete while still mounted will no longer appear in useFetchers() after completion - they served no purpose in there since you can access the data via useFetcher().data
- Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state
  - They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount
  - If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
  - However, if a fetcher was re-mounted elsewhere in the tree using the same key, then it's result will be processed, even if the originating fetcher was unmounted

Patch Changes

@remix-run/express: Allow the Express adapter to work behind a proxy when using app.enable('trust proxy') (#7323)
- Previously, this used req.get('host') to construct the Remix Request, but that does not respect X-Forwarded-Host
- This now uses req.hostname which will respect X-Forwarded-Host
@remix-run/react: Fix warning that could be inadvertently logged when using route files with no default export (#7745)
create-remix: Support local tarballs with a .tgz extension which allows direct support for pnpm pack tarballs (#7649)
create-remix: Default the Remix app version to the version of create-remix being used (#7670)
- This most notably enables easier usage of tags, e.g. npm create remix@nightly

Updated Dependencies

Changes by Package

Full Changelog: 2.1.0...2.2.0

Assets 2

16 Oct 16:49

brophdawg11

remix@2.1.0

4c1047d

v2.1.0

Minor Changes

View Transitions 🚀

We're excited to release experimental support for the the View Transitions API in Remix! You can now trigger navigational DOM updates to be wrapped in document.startViewTransition to enable CSS animated transitions on SPA navigations in your application. (#10916)

The simplest approach to enabling a View Transition in your Remix app is via the new <Link unstable_viewTransition> prop. This will cause the navigation DOM update to be wrapped in document.startViewTransition which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

If you need to apply more fine-grained styles for your animations, you can leverage the unstable_useViewTransitionState hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

function ImageLink(to, src, alt) {
  const isTransitioning = unstable_useViewTransitionState(to);
  return (
    <Link to={to} unstable_viewTransition>
      <img
        src={src}
        alt={alt}
        style={{
          viewTransitionName: isTransitioning ? "image-expand" : "",
        }}
      />
    </Link>
  );
}

You can also use the <NavLink unstable_viewTransition> shorthand which will manage the hook usage for you and automatically add a transitioning class to the <a> during the transition:

a.transitioning img {
  view-transition-name: "image-expand";
}

<NavLink to={to} unstable_viewTransition>
  <img src={src} alt={alt} />
</NavLink>

For an example usage of View Transitions, check out our fork of the Astro Records demo (which uses React Router but so does Remix 😉).

For more information on using the View Transitions API, please refer to the Smooth and simple transitions with the View Transitions API guide from the Google Chrome team.

Stable `createRemixStub` 🔒

After real-world experience, we're confident in the createRemixStub API and ready to commit to it, so in 2.1.0 we've removed the unstable_ prefix. (#7647)

⚠️ Please note that this did involve 1 small breaking change - the <RemixStub remixConfigFuture> prop has been renamed to <RemixStub future> to decouple the future prop from a specific file location.

Patch Changes

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
- This fixes type errors when upgrading to v2 from 1.19
Avoid mutating meta object when tagName is specified (#7594)
Fix FOUC on subsequent client-side navigations to route.lazy routes (#7576)
Export the proper Remix useMatches wrapper to fix UIMatch typings (#7551)
@remix-run/cloudflare - sourcemap takes into account special chars in output file (#7574)
@remix-run/express - Flush headers for text/event-stream responses (#7619)

Changes by Package

Full Changelog: 2.0.1...2.1.0

Assets 2

21 Sep 22:24

brophdawg11

remix@2.0.1

27ee4fc

v2.0.1

Patch Changes

Fix types for MDX files when using pnpm (#7491)
Update getDependenciesToBundle to handle ESM packages without main exports (#7272)
- Note that these packages must expose package.json in their exports field so that their path can be resolved
Fix server builds where serverBuildPath extension is .cjs (#7180)
Fix HMR for CJS projects using remix-serve and manual mode (remix dev --manual) (#7487)
- By explicitly busting the require cache, remix-serve now correctly re-imports new server changes in CJS
- ESM projects were already working correctly and are not affected by this.
Fix error caused by partially written server build (#7470)
- Previously, it was possible to trigger a reimport of the app server code before the new server build had completely been written. Reimporting the partially written server build caused issues related to build.assets being undefined and crashing when reading build.assets.version
Add second generic to UIMatch for handle field (#7464)
Fix resource routes being loaded through route.lazy (#7498)
Throw a semantically correct 405 ErrorResponse instead of just an Error when submitting to a route without an action (#7423)
Update to latest version of @remix-run/web-fetch (#7477)
Switch from crypto.randomBytes to crypto.webcrypto.getRandomValues for file session storage ID generation (#7203)
Use native Blob class instead of polyfill (#7217)

Changes by Package 🔗

Full Changelog: 2.0.0...2.0.1

Assets 2

15 Sep 17:59

brophdawg11

remix@2.0.0

e547efd

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially requires:

React 18 (#7121)
- For information on upgrading to React 18, please see the React upgrade guide
Node 18 or later (#6939, #7292)
- For information on upgrading to Node 18, please see the Node v18 announcement
- Please refer to the Remix documentation for an overview of when we drop support for Node versions

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

v2_dev - New dev server with HMR+HDR (#7002)
- If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
v2_headers - Altered the logic for headers in nested route scenarios (#6979)
v2_meta - Altered the return format of meta() (#6958)
v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

remix.config.js
- Renamed browserBuildDirectory to assetsBuildDirectory (#6900)
- Removed devServerBroadcastDelay (#7063)
- Renamed devServerPort to dev.port (000457e0)
  - Note that if you are opting into this in a 1.x release, your config flag will be future.v2_dev.port, but on a stable 2.x release it will be dev.port
- Changed the default serverModuleFormat from cjs to esm (#6949)
- Removed serverBuildTarget (#6896)
- Changed serverBuildDirectory to serverBuildPath (#6897)
- Node built-ins are no longer polyfilled on the server by default, you must opt-into polyfills via serverNodeBuiltinsPolyfill (#6911
@remix-run/react
- Removed useTransition (#6870)
- Removed fetcher.type and flattened fetcher.submission (#6874)
  - <fetcher.Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET request
- Require camelCased versions of imagesrcset/imagesizes (#6936)

Without deprecation warnings

Unfortunately, we didn't manage to get a deprecation warning on every breaking change or API removal 🙃. Here's a list of remaining changes that you may need to look into to upgrade to v2:

remix.config.js
- Node built-ins are no longer polyfilled in the browser by default, you must opt-into polyfills via browserNodeBuiltinsPolyfill (#7269)
- PostCSS/Tailwind will be enabled by default if config files exist in your app, you may disable this via the postcss and tailwind flags (#6909)
@remix-run/cloudflare
- Remove createCloudflareKVSessionStorage (#6898)
- Drop @cloudflare/workers-types v2 & v3 support (#6925)
@remix-run/dev
- Removed REMIX_DEV_HTTP_ORIGIN in favor of REMIX_DEV_ORIGIN (#6963)
- Removed REMIX_DEV_SERVER_WS_PORT in favor of dev.port or --port (#6965)
- Removed --no-restart/restart flag in favor of --manual/manual (#6962)
- Removed --scheme/scheme and --host/host in favor of REMIX_DEV_ORIGIN instead (#6962)
- Removed the codemod command (#6918)
@remix-run/eslint-config
- Remove @remix-run/eslint-config/jest config (#6903)
- Remove magic imports ESLint warnings (#6902)
@remix-run/netlify
- The @remix-run/netlify adapter has been removed in favor of the Netlify official adapters (#7058)
@remix-run/node
- fetch is no longer polyfilled by default - apps must call installGlobals() to install the polyfills (#7009)
- fetch and related APIs are no longer exported from @remix-run/node - apps should use the versions in the global namespace (#7293)
- Apps must call sourceMapSupport.install() to setup source map support
@remix-run/react
- Remove unstable_shouldReload in favor of shouldRevalidate (#6865)
@remix-run/serve
- remix-serve picks an open port if 3000 is taken and PORT is not specified (#7278)
- Integrate manual mode (#7231)
- Remove undocumented createApp Node API (#7229)
- Preserve dynamic imports in remix-serve for external bundle (#7173)
@remix-run/vercel
- The @remix-run/vercel adapter has been removed in favor of out of the box functionality provided by Vercel (#7035)
create-remix
- Stop passing isTypeScript to remix.init script (#7099)
remix
- Removed magic exports ([#6895](https://github.com/re...

Assets 2

09 Aug 16:32

brophdawg11

remix@1.19.3

21d2290

v1.19.3

Patch Changes

Show deprecation warning when using devServerBroadcastDelay and devServerPort config options (#7064)

Changes by Package 🔗

@remix-run/dev

Full Changelog: 1.19.2...1.19.3

Assets 2

04 Aug 11:05

brophdawg11

remix@1.19.2

33558d3

v1.19.2

Patch Changes

Show deprecation warning on @remix-run/netlify usage, which is deprecated in favor of @netlify/remix-adapter (#6937)
Update to latest @remix-run/web-* packages (#7026)
Install source-map-support in @remix-run/serve (#7039)
Update proxy-agent to resolve npm audit security vulnerability (#7027)

Changes by Package 🔗

Full Changelog: 1.19.1...1.19.2

Assets 2

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Minor Changes

Vite!

New APIs in `@remix-run/dev`

Changed APIs

Other Runtimes

New Fetcher APIs

Persistence Future Flag (`future.v3_fetcherPersist`)

Patch Changes

Updated Dependencies

Changes by Package

Minor Changes

View Transitions 🚀

Stable `createRemixStub` 🔒

Patch Changes

Changes by Package

Patch Changes

Changes by Package 🔗

Remix v2

Breaking Changes

Upgraded Dependency Requirements

Removed Future Flags

Breaking Changes/API Removals

With deprecation warnings

Without deprecation warnings

Patch Changes

Changes by Package 🔗

Patch Changes

Changes by Package 🔗

Releases: remix-run/remix

v2.4.1

v2.4.0

v2.3.1

v2.3.0

v2.2.0

Minor Changes

Vite!

New APIs in @remix-run/dev

Changed APIs

Other Runtimes

New Fetcher APIs

Persistence Future Flag (future.v3_fetcherPersist)

Patch Changes

Updated Dependencies

Changes by Package

v2.1.0

Minor Changes

View Transitions 🚀

Stable createRemixStub 🔒

Patch Changes

Changes by Package

v2.0.1

Patch Changes

Changes by Package 🔗

v2.0.0

Remix v2

Breaking Changes

Upgraded Dependency Requirements

Removed Future Flags

Breaking Changes/API Removals

With deprecation warnings

Without deprecation warnings

v1.19.3

Patch Changes

Changes by Package 🔗

v1.19.2

Patch Changes

Changes by Package 🔗

New APIs in `@remix-run/dev`

Persistence Future Flag (`future.v3_fetcherPersist`)

Stable `createRemixStub` 🔒