feat(RSC): Remove deprecations and RSC-first docs

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -29,9 +29,8 @@ body:
       label: Mandatory reproduction URL (CodeSandbox or GitHub repository)
       description: |
         **Templates:**
-        - [CodeSandbox (`app` directory)](https://codesandbox.io/p/sandbox/next-intl-bug-template-forked-yow8ep)
-        - [CodeSandbox (`app` directory, RSC beta)](https://codesandbox.io/p/sandbox/next-intl-bug-template-app-forked-zcymvq)
-        - [CodeSandbox (`pages` directory)](https://codesandbox.io/p/sandbox/next-intl-bug-template-pages-krm37f)
+        - [CodeSandbox (App Router)](https://codesandbox.io/p/sandbox/next-intl-bug-template-app-forked-zcymvq)
+        - [CodeSandbox (Pages Router)](https://codesandbox.io/p/sandbox/next-intl-bug-template-pages-krm37f)
     validations:
       required: true
   - type: textarea

docs/components/CodeSnippets.tsx

@@ -348,7 +348,7 @@ function buildOutput() {
         <span style={{color: 'var(--shiki-color-text)'}}> kB</span>
         <span style={{color: 'var(--shiki-color-text)'}}>{'     '}</span>
         <span style={{color: 'var(--shiki-token-string-expression)'}}>
-          104 kB
+          87.6 kB
         </span>
       </span>
       <span className="line">
@@ -358,7 +358,7 @@ function buildOutput() {
         <span style={{color: 'var(--shiki-color-text)'}}> B</span>
         <span style={{color: 'var(--shiki-color-text)'}}>{'      '}</span>
         <span style={{color: 'var(--shiki-token-string-expression)'}}>
-          97.5 kB
+          80.2 kB
         </span>
       </span>
       <span className="line">
@@ -368,7 +368,7 @@ function buildOutput() {
         <span style={{color: 'var(--shiki-color-text)'}}> kB</span>
         <span style={{color: 'var(--shiki-color-text)'}}>{'    '}</span>
         <span style={{color: 'var(--shiki-token-string-expression)'}}>
-          106 kB
+          89.3 kB
         </span>
       </span>
       <span className="line"> </span>

docs/next.config.js

@@ -30,12 +30,17 @@ module.exports = withNextra({
     },
     {
       source: '/docs/getting-started/production-checklist',
-      destination: '/docs/production-checklist',
+      destination: '/docs/environments/runtime-requirements',
       permanent: true
     },
     {
       source: '/docs/usage/production-checklist',
-      destination: '/docs/production-checklist',
+      destination: '/docs/environments/runtime-requirements',
+      permanent: true
+    },
+    {
+      source: '/docs/production-checklist',
+      destination: '/docs/environments/runtime-requirements',
       permanent: true
     },
     {
@@ -45,12 +50,22 @@ module.exports = withNextra({
     },
     {
       source: '/docs/next-13/client-components',
-      destination: '/docs/getting-started/app-router-client-components',
+      destination: '/docs/getting-started/app-router',
       permanent: true
     },
     {
       source: '/docs/next-13/server-components',
-      destination: '/docs/getting-started/app-router-server-components',
+      destination: '/docs/getting-started/app-router',
+      permanent: true
+    },
+    {
+      source: '/docs/getting-started/app-router-server-components',
+      destination: '/docs/getting-started/app-router',
+      permanent: true
+    },
+    {
+      source: '/docs/getting-started/app-router-client-components',
+      destination: '/docs/getting-started/app-router',
       permanent: true
     },
     {
@@ -75,22 +90,17 @@ module.exports = withNextra({
     },
     {
       source: '/docs/usage/production-checklist',
-      destination: '/docs/production-checklist',
+      destination: '/docs/environments/runtime-requirements',
       permanent: true
     },
     {
       source: '/docs/usage/runtime-requirements-polyfills',
-      destination: '/docs/production-checklist#runtime-requirements',
-      permanent: true
-    },
-    {
-      source: '/docs/usage/configuration',
-      destination: '/docs/configuration',
+      destination: '/docs/environments/runtime-requirements',
       permanent: true
     },
     {
       source: '/docs/usage/error-handling',
-      destination: '/docs/configuration#error-handling',
+      destination: '/docs/usage/configuration#error-handling',
       permanent: true
     },
     {

docs/pages/blog/index.mdx

@@ -2,8 +2,6 @@ import CommunityLink from 'components/CommunityLink';
 
 # next-intl blog
 
-Failed attempts at writing docs that somehow turned into blog posts.
-
 <div className="flex flex-col gap-4 py-8">
   <CommunityLink
     href="/blog/translations-outside-of-react-components"

docs/pages/blog/translations-outside-of-react-components.mdx

@@ -111,26 +111,21 @@ Additionally, this approach is more robust to possibly unexpected states, like t
 
 If you’re working with Next.js, you might want to translate i18n messages in [API routes](https://nextjs.org/docs/pages/building-your-application/routing/api-routes), [Route Handlers](https://nextjs.org/docs/app/building-your-application/routing/router-handlers) or the [Metadata API](https://nextjs.org/docs/app/api-reference/file-conventions/metadata).
 
-`next-intl` provides a [core library](/docs/environments/core-library) that is agnostic from React and can be used for these cases.
+`next-intl/server` provides a set of awaitable versions of the functions that you usually call as hooks from within components. These are agnostic from React and can be used for these cases.
 
 ```tsx
-import {createTranslator} from 'next-intl';
+import {getTranslator} from 'next-intl/server';
 
-const messages = {
-  hello: 'Hello {name}!'
-};
+// The `locale` is received from Next.js via `params`
+const locale = params.locale;
 
 // This creates the same function that is returned by `useTranslations`.
-// Since there's no provider, you can pass all the properties you'd
-// usually pass to the provider directly here.
-const t = createTranslator({locale: 'en', messages});
+const t = await getTranslator(locale);
 
 // Result: "Hello world!"
 t('hello', {name: 'world'});
 ```
 
-There's currently a proposal to further simplify this use case, by offering a set of [new APIs that integrate with Server Components](/docs/environments/metadata-route-handlers) (currently in beta).
-
 ## This seems familiar
 
 If you’ve been working with React for a longer time, you might have experienced the change [from `component{DidMount,DidUpdate,WillUnmount}` to `useEffect`](https://legacy.reactjs.org/docs/hooks-effect.html#explanation-why-effects-run-on-each-update). The reason why `useEffect` is superior is because it nudges the developer into a direction where the app is always in sync and by doing this, a whole array of potential issues just magically disappear.

docs/pages/docs/_meta.json

@@ -2,9 +2,7 @@
   "getting-started": "Getting started",
   "usage": "Usage guide",
   "environments": "Environments",
-  "configuration": "Global configuration",
   "routing": "Routing",
   "workflows": "Workflows & integrations",
-  "production-checklist": "Production checklist",
   "faq": "FAQ"
 }

docs/pages/docs/environments/_meta.json

@@ -3,5 +3,6 @@
   "server-client-components": "Server & Client Components",
   "metadata-route-handlers": "Metadata & Route Handlers",
   "error-files": "Error files (e.g. not-found)",
-  "core-library": "Core library"
+  "core-library": "Core library",
+  "runtime-requirements": "Runtime requirements"
 }

docs/pages/docs/environments/error-files.mdx

@@ -1,4 +1,3 @@
-import VersionTabs from 'components/VersionTabs';
 import Callout from 'components/Callout';
 
 # Internationalization in Next.js error files
@@ -70,7 +69,7 @@ export default function NotFound() {
 }
 ```
 
-Note that the presence of `app/not-found.tsx` requires that a root layout is available as well, even if it's just passing `children` through.
+Note that the presence of `app/not-found.tsx` requires that a root layout is available, even if it's just passing `children` through.
 
 ```tsx filename="app/layout.tsx"
 // Since we have a root `not-found.tsx` page, a layout file
@@ -89,12 +88,8 @@ import {notFound} from 'next/navigation';
 const locales = ['en', 'de'];
 
 export default function LocaleLayout({children, params}) {
-  const locale = useLocale();
-
-  // Validate that the incoming `locale` parameter is a valid locale
-  if (params.locale !== locale) {
-    notFound();
-  }
+  // Validate that the incoming `locale` parameter is valid
+  if (!locales.includes(locale as any)) notFound();
 
   return (
     <html lang={locale}>
@@ -125,11 +120,7 @@ When an `error` file is defined, Next.js creates [an error boundary within your
 
 </figure>
 
-Since the `error` file must be defined as a Client Component, you have to use [`NextIntlClientProvider`](/docs/configuration#client-server-components) to provide messages in case the `error` file renders.
-
-If you've [set up `next-intl` to be used in Client Components](/docs/getting-started/app-router-client-components), this is already the case and there's no additional setup needed. If you're using [the Server Components beta](/docs/getting-started/app-router-server-components) though, you have to provide the relevant messages in the wrapping layout.
-
-<figure>
+Since the `error` file must be defined as a Client Component, you have to use [`NextIntlClientProvider`](/docs/usage/configuration#nextintlclientprovider) to provide messages in case the `error` file renders.
 
 ```tsx filename="app/[locale]/layout.tsx"
 import pick from 'lodash/pick';
@@ -153,13 +144,6 @@ export default async function LocaleLayout({children}) {
 }
 ```
 
-<figcaption>
-  Providing messages for the `error` file is only necessary when using [the
-  Server Components beta](/docs/getting-started/app-router-server-components).
-</figcaption>
-
-</figure>
-
 Once `NextIntlClientProvider` is in place, you can use functionality from `next-intl` in the `error` file:
 
 ```tsx filename="app/[locale]/error.tsx"
@@ -178,3 +162,5 @@ export default function Error({error, reset}) {
   );
 }
 ```
+
+Note that `NextIntlClientProvider` only provides the messages to your error page, but doesn't load any runtime code for processing translations on the client side. Only the error page will include this code, so the performance of other pages isn't affected.

docs/pages/docs/environments/index.mdx

@@ -36,3 +36,5 @@ The `next-intl` APIs are available in the following environments:
     href="/docs/environments/core-library"
   />
 </div>
+
+While modern browsers and server runtimes typically support all necessary JavaScript APIs that are required for `next-intl`, you can double check [the runtime requirements](/docs/environments/runtime-requirements).