Jan Amann
Jan Amann
> Right, I'm also not a fan of this. But I believe at least for the case you mentioned above about without chunks, worth documenting it and updating the types....
Awesome! 👏
I've added https://github.com/amannn/next-intl/issues/1285 to investigate a better way to achieve global error handling.
Just benchmarked this again, and I think we should really cache the constructors: - [`Intl.NumberFormat`](https://jsperf.app/yoqoso/2) - [`Intl.DateTimeFormat`](https://jsperf.app/mateho)
@questionableservices This is discussed in https://github.com/amannn/next-intl/issues/444.
> SSG doesn't support per-domain generation Yep, this is unfortunately quite difficult. The only workaround I know of is a dynamic segment like `app/[domain]` but it seems a bit backward...
It would enable static rendering, yes, but you end up with an invalid `locale` parameter that requires deserialization. If you're rewriting the whole middleware & navigation APIs anyway, you could...
While working on https://github.com/amannn/next-intl/pull/1017 I noticed that if Next.js would support a way to [read params deeply](https://github.com/vercel/next.js/discussions/58862), we could enable the user to match any kind of URL structure to...
Good news, I've added built-in support for custom prefixes in https://github.com/amannn/next-intl/pull/1086! There's a pre-release available, so if you'd like to give this a spin and provide feedback, that would be...
Adding the prefix for `getPathname` was also discussed in https://github.com/amannn/next-intl/discussions/785#discussioncomment-8159571.