My site paths are like - https://www.example.com/us/en/products https://www.example.com/us/es/products https://www.example.com/us/en/categories https://www.example.com/us/es/categories or - https://www.example.com/[countryCode]/[languageCode]/products Though libraries like - next-intl provides a way to deal with languages only but not if it has some previous country code attached to it. Let me…
Since I added the config file and replace : Navigation File import { createLocalizedPathnamesNavigation, Pathnames } from 'next-intl/navigation'; By : Config File import {Pathnames, LocalePrefix} from 'next-intl/routing';} Navigation File import { createLocalizedPathnamesNavigation } from "next-intl/navigation"; import { locales, pathnames, localePrefix…
I am using nextjs 14 and just integrated next-intl for internationalization. My Problem: If I switch between the browse and my-items page, the fetch script, and the page rendering twice My questions: 1, Why does it happen? 2, How can…
I have a NExt JS project using the app router with Supabase. I have a ROOT middleware.js file that contains some supabase code. I also need to integrate Next-Intl middleware into this too and i'm not sure how to go…
I'm working with Next.js 14 and next-intl and trying to set up a routing mechanism where different paths render the same component based on the pathname. My application is multilingual, and each language version has its own URL path but…
I implemented a next-intl for multi-language support. So my paths look like www.next.com/de or www.next.com/en I'm using NextJS 14. <NextLink href="/support-us">{t("About us")}</NextLink> And when I want to navigate to for example /support-us it must navigate me to /en/support-us instead I…
I'm currently utilizing Next.js (v13.5.4) and next-intl (v3.0.0-beta.19) for internationalization. My goal is to modify the URL structure for locales from a format like en-GB to en/UK. I've set up Next with the app router and initialized next-intl following the…