Jan Amann

@AdamQuadmon Sorry, I don't quite understand your question. The discussion in this issue is about having a different `localePrefix` per domain. If there's a locale prefix, you'll use the setup...

> Initially I was investigating why `localePrefix: 'never'` was not respected in my configuration with different domains. Hmm, not sure either—feel free to open an issue if you have a...

Hey, thanks for proposing this change! We do in fact already have docs for how to compose the `Link` with its `href` prop in case of localized pathnames: [`Link`](https://next-intl-docs.vercel.app/docs/routing/navigation#link) (click...

There was an FAQ section at some point but it ended up just collecting random stuff that didn't fit anywhere else better 🙂. I found that it's better to provide...

I'm going to close this for the time being as there are already docs about composing the `href` prop. Thanks for the input though @ScreamZ!

I have a similar situation. I have two processes and would like to use `--hide 1 --raw`, so that only the output from the first process is displayed. Unfortunately, `--raw`...

Hey, thanks for the report! I tried reproducing it but no luck unfortunately yet: https://github.com/amannn/next-intl/assets/4038316/c1743dac-9dfb-479d-973c-634f1f2c9cba Am I doing something wrong here?

Btw. in the lockfile of your repro is a slightly outdated version of next-intl. I couldn’t reproduce the issue after updating, but maybe you want to upgrade nonetheless in case...

Interesting, not sure why you're seeing a different result. There is however something related I saw recently that could explain this bug. Reproduction: 1. Go to https://next-intl-example-next-13.vercel.app/en (`NEXT_LOCALE` cookie is...

I made some progress in regard to this in https://github.com/amannn/next-intl/pull/790. After hitting a blocker, I wanted to submit a bug report to Next.js, but found that the latest canary version...