Don't force to add untranslatable pathnames to pathnames: {} in routing.ts

[alexclinky]

Hi,

I am referring to this:
https://next-intl.dev/docs/routing/configuration#pathnames

If my app has 100 pages, I don't want to add paths that i don't need translations. If I don't I get an error from

import { Link } from "@/i18n/navigation";

[amannn]

You can either opt-ouf for specific cases, or you can disable type safety altogether with something like:

import {defineRouting} from 'next-intl/routing';

export const routing = defineRouting({
  locales: ['en', 'de'],
  defaultLocale: 'en',
  pathnames: {
    '/pathnames': {
      de: '/pfadnamen'
    }
  } as any // This disables validation of pathnames
});

If there's no matching entry in your config, next-intl will fall back to assuming no translated variants are available.