fix(RSC): Always read header in RSC render

[amannn]

Should fix #446

As far as I understand the issue currently, something like this happens:

1. The middleware receives a request where the NEXT_LOCALE cookie is set
2. During the RSC render, the NEXT_LOCALE cookie is suddenly not available

If this is the case, this would fix the issue.

If however the middlware doesn't run at all for some reason, this will not make a difference. However, since this doesn't seem to have any downsides (possible since newer Next.js versions), this might simplify the code anyway and is a welcome change.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-intl-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 14, 2023 7:23am
next-intl-example-next-13	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 14, 2023 7:23am

[carlosmca44]

At this moment I get a new error that I don't know if it has to do with nextjs 13.5.4 or with next-intl. The thing is that in all the tutorials that I have seen and even documentation, everywhere in the rootlayout they use the useLocale() hook and no one has a problem, it does give me a problem since it is a hook and the hooks cannot be server side
The error shown is the following:

 ✓ Compiled in 761ms (1242 modules)
 ⨯ node_modules/next-intl/dist/esm/server/RequestLocale.js (1:580) @ eval
 ⨯ Error: Unable to find `next-intl` locale, have you configured the middleware?`
    at RootLayout (./src/app/[locale]/layout.tsx:29:73)
    at async Promise.all (index 0)
null

My configuration is to the letter with the documentation and on par with other programmers, but no one else gets the same error as me, or at least for the same reason.
I will be really thankful if you or anybody can help me with this problem.

[matee-safi]

I get the same error as well