v1.118.0

Compare Source

v7.32.1

Compare Source

v7.32.0

Compare Source

Minor Changes

• Icons: Updated SignLanguageTwoHands-design. (#​4115)

• Icons: 🎉 Added some new icons ChairTable, Footprint, Lifebuoy, OpenBook, OpenMagazine and Slide. (#​4115)

v7.9.4

Compare Source

Patch Changes

• Update valibot dependency to ^1.1.0 (#​14379)

• New (unstable) useRoute hook for accessing data from specific routes (#​14407)

  For example, let's say you have an admin route somewhere in your app and you want any child routes of admin to all have access to the loaderData and actionData from admin.

  // app/routes/admin.tsx
  import { Outlet } from "react-router";
  
  export const loader = () => ({ message: "Hello, loader!" });
  
  export const action = () => ({ count: 1 });
  
  export default function Component() {
    return (
      <div>
        {/* ... */}
        <Outlet />
        {/* ... */}
      </div>
    );
  }

  You might even want to create a reusable widget that all of the routes nested under admin could use:

  import { unstable_useRoute as useRoute } from "react-router";
  
  export function AdminWidget() {
    // How to get `message` and `count` from `admin` route?
  }

  In framework mode, useRoute knows all your app's routes and gives you TS errors when invalid route IDs are passed in:

  export function AdminWidget() {
    const admin = useRoute("routes/dmin");
    //                      ^^^^^^^^^^^
  }

  useRoute returns undefined if the route is not part of the current page:

  export function AdminWidget() {
    const admin = useRoute("routes/admin");
    if (!admin) {
      throw new Error(`AdminWidget used outside of "routes/admin"`);
    }
  }

  Note: the root route is the exception since it is guaranteed to be part of the current page.
  As a result, useRoute never returns undefined for root.

  loaderData and actionData are marked as optional since they could be accessed before the action is triggered or after the loader threw an error:

  export function AdminWidget() {
    const admin = useRoute("routes/admin");
    if (!admin) {
      throw new Error(`AdminWidget used outside of "routes/admin"`);
    }
    const { loaderData, actionData } = admin;
    console.log(loaderData);
    //          ^? { message: string } | undefined
    console.log(actionData);
    //          ^? { count: number } | undefined
  }

  If instead of a specific route, you wanted access to the current route's loaderData and actionData, you can call useRoute without arguments:

  export function AdminWidget() {
    const currentRoute = useRoute();
    currentRoute.loaderData;
    currentRoute.actionData;
  }

  This usage is equivalent to calling useLoaderData and useActionData, but consolidates all route data access into one hook: useRoute.

  Note: when calling useRoute() (without a route ID), TS has no way to know which route is the current route.
  As a result, loaderData and actionData are typed as unknown.
  If you want more type-safety, you can either narrow the type yourself with something like zod or you can refactor your app to pass down typed props to your AdminWidget:

  export function AdminWidget({
    message,
    count,
  }: {
    message: string;
    count: number;
  }) {
    /* ... */
  }

• Updated dependencies:

  • react-router@7.9.4
  • @react-router/node@7.9.4
  • @react-router/serve@7.9.4

v7.9.4

Compare Source

Patch Changes

• Validate format of incoming session ids (#​14426)
• Updated dependencies:
  • react-router@7.9.4

v7.9.4

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.4
  • @react-router/node@7.9.4
  • @react-router/express@7.9.4

v16.0.3

2025-10-13

Bugfixes

• fix: resolve bare targets of package "imports" using export maps; avoid fileURLToPath(null) (#​1908)

v25.6.0

Compare Source

• feat: exists() method now respects returnObjects option - returns false when accessing an object key with returnObjects: false, enabling detection of object vs string keys 2359

  Note: This is a potential behavior change. If you were previously calling exists() with returnObjects: false on object keys, those calls will now return false instead of true. This enables developers to detect whether a key points to an object or string value.

v1.56.0

Compare Source

v10.18.2

Compare Source

Patch Changes

• pnpm outdated --long should work #​10040.
• Replace ndjson with split2. Reduce the bundle size of pnpm CLI #​10054.
• pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #​9963.
• pnpm version switching should work when the pnpm home directory is in a symlinked directory #​9715.
• Fix EPIPE errors when piping output to other commands #​10027.

v10.18.1

Compare Source

Patch Changes

• Don't print a warning, when --lockfile-only is used #​8320.
• pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #​5700.
• When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

v7.9.4

Compare Source

Patch Changes

• handle external redirects in from server actions (#​14400)

• New (unstable) useRoute hook for accessing data from specific routes (#​14407)

  For example, let's say you have an admin route somewhere in your app and you want any child routes of admin to all have access to the loaderData and actionData from admin.

  // app/routes/admin.tsx
  import { Outlet } from "react-router";
  
  export const loader = () => ({ message: "Hello, loader!" });
  
  export const action = () => ({ count: 1 });
  
  export default function Component() {
    return (
      <div>
        {/* ... */}
        <Outlet />
        {/* ... */}
      </div>
    );
  }

  You might even want to create a reusable widget that all of the routes nested under admin could use:

  import { unstable_useRoute as useRoute } from "react-router";
  
  export function AdminWidget() {
    // How to get `message` and `count` from `admin` route?
  }

  In framework mode, useRoute knows all your app's routes and gives you TS errors when invalid route IDs are passed in:

  export function AdminWidget() {
    const admin = useRoute("routes/dmin");
    //                      ^^^^^^^^^^^
  }

  useRoute returns undefined if the route is not part of the current page:

  export function AdminWidget() {
    const admin = useRoute("routes/admin");
    if (!admin) {
      throw new Error(`AdminWidget used outside of "routes/admin"`);
    }
  }

  Note: the root route is the exception since it is guaranteed to be part of the current page.
  As a result, useRoute never returns undefined for root.

  loaderData and actionData are marked as optional since they could be accessed before the action is triggered or after the loader threw an error:

  export function AdminWidget() {
    const admin = useRoute("routes/admin");
    if (!admin) {
      throw new Error(`AdminWidget used outside of "routes/admin"`);
    }
    const { loaderData, actionData } = admin;
    console.log(loaderData);
    //          ^? { message: string } | undefined
    console.log(actionData);
    //          ^? { count: number } | undefined
  }

  If instead of a specific route, you wanted access to the current route's loaderData and actionData, you can call useRoute without arguments:

  export function AdminWidget() {
    const currentRoute = useRoute();
    currentRoute.loaderData;
    currentRoute.actionData;
  }

  This usage is equivalent to calling useLoaderData and useActionData, but consolidates all route data access into one hook: useRoute.

  Note: when calling useRoute() (without a route ID), TS has no way to know which route is the current route.
  As a result, loaderData and actionData are typed as unknown.
  If you want more type-safety, you can either narrow the type yourself with something like zod or you can refactor your app to pass down typed props to your AdminWidget:

  export function AdminWidget({
    message,
    count,
  }: {
    message: string;
    count: number;
  }) {
    /* ... */
  }

v7.9.4

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.4

v7.4.2

Compare Source

What's Changed

New Features

• Deprecate useLocale and useChangeLanguage hooks by @​sergiodxa in #​358

Full Changelog: sergiodxa/remix-i18next@v7.4.1...v7.4.2

v7.4.1

Compare Source

What's Changed

New Features

• Add react-i18next v16 to peerDependencies by @​akinorimizushima in #​343

Other Changes

• Bump @​types/react from 19.1.13 to 19.1.15 by @​dependabot[bot] in #​344
• Bump @​types/bun from 1.2.22 to 1.2.23 by @​dependabot[bot] in #​345
• Bump react-i18next from 15.7.1 to 16.0.0 by @​dependabot[bot] in #​346
• Bump i18next from 25.4.0 to 25.5.2 by @​dependabot[bot] in #​347
• Bump react-router from 7.9.1 to 7.9.3 by @​dependabot[bot] in #​348
• Bump actions/checkout from 4 to 5 by @​dependabot[bot] in #​349
• Bump @​biomejs/biome from 2.2.4 to 2.2.5 by @​dependabot[bot] in #​352
• Bump react-dom from 19.1.1 to 19.2.0 by @​dependabot[bot] in #​353
• Bump react and @​types/react by @​dependabot[bot] in #​354
• Bump typescript from 5.9.2 to 5.9.3 by @​dependabot[bot] in #​355

New Contributors

• @​akinorimizushima made their first contribution in #​343

Full Changelog: sergiodxa/remix-i18next@v7.4.0...v7.4.1

v4.1.12

Compare Source