fix(intl): safeguard against missing translation keys and resolve middleware naming conflict
Some checks failed
🚀 Build & Deploy / 🔍 Prepare (push) Successful in 4s
🚀 Build & Deploy / 🧪 QA (push) Failing after 3m21s
🚀 Build & Deploy / 🚀 Deploy (push) Has been cancelled
🚀 Build & Deploy / 🧪 Post-Deploy Verification (push) Has been cancelled
🚀 Build & Deploy / 🔔 Notify (push) Has been cancelled
🚀 Build & Deploy / 🏗️ Build (push) Has been cancelled

This commit is contained in:
2026-05-04 16:23:28 +02:00
parent 52480b4f55
commit 503676dab5
2 changed files with 5 additions and 1 deletions

18
middleware.ts Normal file
View File

@@ -0,0 +1,18 @@
import createMiddleware from "next-intl/middleware";
export default createMiddleware({
// A list of all locales that are supported
locales: ["de"],
// Used when no locale matches
defaultLocale: "de",
// Use default locale without prefix
localePrefix: "as-needed",
});
export const config = {
// Matcher for all pages and internationalized pathnames
// excluding api, _next, static files, etc.
matcher: ["/((?!api|_next|.*\\..*).*)"],
};