chore(deps): update dependency nextjs-routes to v2.2.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nextjs-routes	2.2.1 -> 2.2.3

---

Release Notes

tatethurston/nextjs-routes (nextjs-routes)

v2.2.3

Compare Source

• Bug fix: usePathname and useParams were incorrectly resolving to any return types.

v2.2.2

Compare Source

• Adds support for Next.js's app directory. Link accepts either static routes (no url parameters) or a RouteLiteral string, which can be generated by the route helper from this library:

  import { route } from "nextjs-routes";
  
  <Link
    href={route({
      pathname: "/foos/[foo]",
      query: { foo: "bar" },
    })}
  >
    Baz
  </Link>;

• Add RouteLiteral type. This type represents a string that has been confirmed to be a validated application route and can be passed to Link or useRouter. This is a TypeScript branded type.

  import { RouteLiteral } from "nextjs-routes";

  route returns a RouteLiteral. If you construct a route string you can cast it to a RouteLiteral so that Link and useRouter will accept it:

  const myRoute = `/foos/${foo}` as RouteLiteral
  

  In general, prefer using the route helper to generate routes.

• Refine types for usePathname, useRouter and useParams from "next/navigation" to use nextjs-routes generated types.

• Fix generated routes when using parallel-routes and intercepting-routes.

• Fix ref type for Link. Previously ref was missing, now it's correctly typed.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.