Statically typed links for Link returned from createSharedPathnamesNavigation

[amannn]

Is your feature request related to a problem? Please describe.

Next.js now supports statically typed links, we should support this too in Link that is returned from createSharedPathnamesNavigation. Also rewrites/redirects should be supported now (needs to be validated).

Note that the Link that is returned from createLocalizedPathnamesNavigation is already statically typed, this issue only applies to createSharedPathnamesNavigation.

Describe the solution you'd like

Compose existing types from Next.js for static typing to work

Describe alternatives you've considered

Leaving the routes untyped as string.

[Aperrix]

up pls ?

[amannn]

I'm currently working on pathname localization in #426 (see details in #402). This will introduce statically typed links when using this feature.

However it would still be cool if we can statically validate links when not using localized pathnames, so I'll leave this issue open for now.

[tacomanator]

Since the two issues referenced are closed, can I safely assume localized routes are typed checked? I could not find relevant docs, but so far I'm having no luck and want to make sure I'm not trying to make something work that simply wont.

typedRoutes is enabled in next config, and using the <Link /> component from createSharedPathnamesNavigation as described in the docs:

import { locales } from "@/i18n";
import { createSharedPathnamesNavigation } from "next-intl/navigation";

export const localePrefix = "always"; // Default

export const { Link, redirect, usePathname, useRouter } =
createSharedPathnamesNavigation({ locales, localePrefix });

but the Link exported from here does not give me type errors bad urls:

import { Link } from "@/navigation";

export default function Index() {
  return (<Link href="/invalidpath">invalid path</Link>); // no type error
}

[amannn]

@tacomanator createSharedPathnamesNavigation currently doesn't provide static typechecking, only createLocalizedPathnamesNavigation does. I've updated the initial feature request accordingly now.

Contributions are welcome for this feature btw., in case someone is interested in looking into it!