Jan Amann
Jan Amann
> we can parse the version from `package.json` or node_modules I thought about that too, but I'm afraid there could be edge cases. E.g., can we make an assumption about...
This was resolved in [v4.0.3](https://github.com/amannn/next-intl/releases/tag/v4.0.3)
Hey @samcx, I hope it's ok for me to chime in. I've tested with the latest canary and am observing the same behavior as you do: In development, only the...
Awesome, thanks a lot @samcx!
@samcx I've just tried out Next.js 15 RC 2 and this issue is still present. Are you working on a fix? I also noticed this affects `next/image` if `priority` is...
@samcx Unfortunately, this is still the case in the stable release of Next.js 15. Are there plans to fix this? As mentioned in my previous comment, this header is critical...
Got it, thanks!
@jefer94 A [sitemap](https://next-intl-docs.vercel.app/docs/environments/actions-metadata-route-handlers#sitemap) with alternate entries can also be a good alternative as long as Next.js has this bug.
@samcx Could the error originate from React [providing its own `Link` header](https://github.com/facebook/react/blob/main/packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js#L6292) that is not merged with the one a user might has set on response headers in the middleware?
I've opened a PR: https://github.com/vercel/next.js/pull/73431