Jón Trausti
Jón Trausti
That's precisely how I do it. ``` export async function getStaticProps({ params, locale, previewData, }: GetStaticPropsContext) { ``` Locale defaults to en. ``` i18n: { locales: ["en", "is"], localeDetection: false,...
Same issue. My guess is that this PR broke it: https://github.com/vercel/next.js/pull/54813/files
Client-side routing is also broken with localization when middleware file is present. The locale always becomes the default locale when clicking on a `` that routes to something such as...
Based on how things are done in Nextjs App router, I don't really see a fix coming any time soon (almost feels like we're being pushed to the App router)....
I ended up removing all NextJS specific locales, which means I had to create a language slug for each language and do some other manual things. In the end it...
Same with some icelandic letters, e.g. if I want to type á, then I first type ´ and then a to get á. For some reason this fails in kbar....
I've been running into the same issue with several packages such as `react-content-loader` and the workaround mentioned above seems to work for my case too.
Still broken for me in 13.5.1 if middleware is being used, even though the middleware is not even triggered for the paths. It just needs to exist. Ref: https://github.com/vercel/next.js/issues/54217
I see, that makes the middleware run for every URL even though it's not needed (more costly AFAIK). But either way this is still a bug.
+1 It would be very useful with Auth0 since `getAccessTokenSilently` is async.