Tom Lienard comments

Results 163 comments of


                                            Tom Lienard

Error when testing `TypeError: (0 , import_react2.cache) is not a function`

Are you using `next/jest.js` inside your Jest configuration?

app-static-to-dynamic-error with generateMetadata using getI18n on page not found

> It would be nice if the params.locale value was always a valid locale. Agree, that's why we use `generateStaticParams` to make sure the dynamic params are valid. This again...

[ RFC ] : Redirect to locale on re-visit when saved local is not the default

Interesting point, especially > page at same URL should not be displayed different contents at any given time I'm not sure if bots actually save and reuse cookies across pages...

[ RFC ] : Redirect to locale on re-visit when saved local is not the default

Thanks for the detailed explanation, and this Google best practices guide is really interesting. > i expect if im comming back to a site and my preference was Portuguese, to...

Add an example of implementing custom `Message` component

Sorry for the delay, I started a new job. Could you share your code so we can try to fix the type errors?

'Unsupported locale error' on routes not matched by middleware.

Is your favicon located inside the `[locale]` folder? Otherwise if it's not ignored but should be as specified in your middleware configuration, I believe it's a Next.js bug.

'Unsupported locale error' on routes not matched by middleware.

This is usually caused by: 1) the middleware being miss-configured 2) the `favicon.ico` file being placed inside the `[locale]` folder, which should instead be inside the `app` (or `src`) folder...

Improve/fix `defineLocale` helper to make sure all locales have the correct keys

You might be able to use the `defineLocale()` helper (from `createI18nClient`), though it probably doesn't work well with nested-objects locales. It hasn't been touched and used since a long time,...

[On page enter][Not blocking error] RangeError: A proper locale must be provided

Interesting, I don't know where this `"A proper locale must be provided"` error is coming from though 🤔

Custom 404 page

> My custom not-found.tsx page with [locale] route not working. Could you be more precise? > easy to reproduce Please provide a minimal reproduction. I tried by adding a `not-found.tsx`...