This reverts commit 47239f9.

…currently active pathname for localized pathnames

# Conflicts:
#	packages/next-intl/src/middleware/utils.test.tsx
#	packages/next-intl/src/shared/utils.test.tsx

Ref #1184
Ref #668

…is rendered from a Server Component (#1191)

This should ease the transition from Server to Client Components, as you
don't have to manually pass this prop anymore. If you've previously
passed this prop manually, you can remove this assignment now.

If this is not desired (e.g. because you have a large `formats` object
that you don't want to pass to the client side), you can manually
opt-out via `formats={{}}` on `NextIntlClientProvider` in order to not
provide any formats on the client side.

**BREAKING CHANGE:** There's a very rare chance where this can break
existing behavior. If you're rendering `NextIntlClientProvider` in a
Server Component, you rely on static rendering, but you're not using
`unstable_setRequestLocale` (i.e. you're using hooks like
`useTranslations` exclusively in Client Components), this can opt your
page into dynamic rendering. If this affects you, please provide the
`formats` prop explicitly to `NextIntlClientProvider`.

If you have nested providers, previously only the configuration of the
innermost one would be applied.

With this change, configuration is now passed from one provider to the
next, while allowing to override individual props.

**BREAKING CHANGE:** There's a very rare chance that this change affects
your app, but in case you've previously relied on providers not
inheriting from each other, you now have to reset props manually in case
you want to retain the prev. behavior.

# Conflicts:
#	packages/next-intl/.size-limit.ts

# Conflicts:
#	docs/src/pages/docs/usage/configuration.mdx
#	packages/next-intl/.size-limit.ts
#	packages/use-intl/.size-limit.ts

…transform (#1470)

**Changes**

1. `next-intl` as well as its base library `use-intl` are now ESM-only.
With this, the library is now ~7% smaller and provides full support for
tree shaking. Most tools support ESM out-of-the-box, but some might
require additional configuration (e.g. Jest might benefit from
[`next/jest`](https://nextjs.org/docs/app/building-your-application/testing/jest#manual-setup)).
The only exception is `next-intl/plugin` which is provided both as ESM
as well as CommonJS due to `next.config.js` still being popular.
2. Syntax is compiled down to the Browserslist
[`defaults`](https://github.com/browserslist/browserslist/blob/065c69b0e1e6ad679263d03e22c605830bbc52e5/index.js#L460)
query, which is a shortcut for `> 0.5%, last 2 versions, Firefox ESR,
not dead`. The `defaults` query was thoroughly designed by the
Browserslist community and is considered a reasonable default for modern
apps. If you target outdated browsers, you can use
[`transpilePackages`](https://nextjs.org/docs/app/api-reference/next-config-js/transpilePackages)
in combination with a
[`browserslist`](https://nextjs.org/docs/architecture/supported-browsers)
config in Next.js to compile `next-intl` for older browsers.
3. The minimum React version is 17 now (which supports the modern JSX
transform)

**Changes**
- Removed deprecated `defaultTranslationValues`
- Remove deprecated detection of `src/i18n.ts` (use
`src/i18n/request.ts` instead, or specify a custom path in your Next.js
config)
- Removed deprecated export of `Pathnames` from `next-intl/navigation`
(still available via `next-intl/routing`)
- Remove deprecated legacy navigation APIs
`createSharedPathnamesNavigation` and
`createLocalizedPathnamesNavigation`

…sing TypeScript (#1481)

If you don't use TypeScript, this change doesn't affect you.

**Changes**
- Removed deprecated second argument of `createMiddleware` (use first
argument instead, ideally via `defineRouting`)
- Remove deprecated `({locale})` argument in `getRequestConfig` (use
`({requestLocale})` instead)
- Remove deprecated `unstable_setRequestLocale` (use `setRequestLocale`
instead)

…arams` when rendered on the client side (#1483)

Bumps the Next.js peer dependency to 13.3.

…cessary and only disable cookie if `localeCookie: false` is set (#1487)

**Changes**
1. The `maxAge` attribute of the locale cookie is decreased from 1 year
to 5 hours in order to be GDPR-compliant.
2. The locale cookie is now only set when the user's language doesn't
match a requested locale. E.g. a user with `accept-language: 'en'` will
cause a cookie to be set when `/de` is requested to remember the
preference for `de`.
3. `localeDetection: false` previously ambiguously also disabled the
cookie from being set. This is no longer the case. For consistency, you
can now use the explicit [`localeCookie:
false`](https://next-intl-docs.vercel.app/docs/routing#locale-cookie)
option instead.

If you want to increase the cookie expiration, you can use the
[`maxAge`](https://next-intl-docs.vercel.app/docs/routing#locale-cookie)
attribute to do so:

```tsx
import {defineRouting} from 'next-intl/routing';
 
export const routing = defineRouting({
  // ...
 
  localeCookie: {
    // Expire in one year
    maxAge: 60 * 60 * 24 * 365
  }
});
```

…es` (#1489)

If consumers use type-safe `IntlMessages`, these will now be used for
`useMessages` and `getMessages`.

Fixes #1452

**Changes**
- Revamps the API to augment types by getting rid of the global
`IntlMessages` and `IntlFormats` in favor of a more general `AppConfig`
that is scoped to `next-intl`.
- Adds support for strictly-typing the locale across `useLocale` as well
as the navigation APIs.
- Adds `import {Locale} from 'next-intl';` as a convenience API to be
reused wherever a `locale` is passed around.
- Add `hasLocale(locales, candidate)` API for simplified checking of
whether a locale is available with TypeScript.
- Adds a new `import {Messages} from 'next-intl;` type that corresponds
to the `Messages` you've provided in `AppConfig` (probably rarely
needed).


**Example:**

```tsx
// global.d.ts

import {routing} from '@/i18n/routing';
import {formats} from '@/i18n/request';
import en from './messages/en.json';

declare module 'next-intl' {
  interface AppConfig {
    Locale: (typeof routing.locales)[number];
    Formats: typeof formats;
    Messages: typeof en;
  }
}
```

**→ [Proposed
docs](https://next-intl-docs-git-feat-augmented-config-next-intl.vercel.app/docs/workflows/typescript)**

Fixes #1377

```json
{
  "UserProfile": {
    "title": "Hello {firstName}"
  }
}
```

```tsx
function UserProfile({user}) {
  const t = useTranslations('UserProfile');
 
  // ✖️ Missing argument
  t('title');
 
  // ✅ Argument is provided
  t('title', {firstName: user.firstName});
}
```

**Changes**
- ICU arguments can now be validated with TypeScript (however, currently
this is
[opt-in](https://next-intl-docs-git-feat-type-safe-params-next-intl.vercel.app/docs/workflows/typescript#messages-arguments))
- `undefined` and `null` are no longer accepted as values for calls to
`t`—please only provide valid values.

Fixes #410

See https://github.com/amannn/next-intl/pull/1523/files#r1832900948

# Conflicts:
#	packages/next-intl/package.json
#	packages/next-intl/src/navigation/react-client/index.tsx
#	packages/next-intl/src/routing/index.tsx
#	packages/next-intl/src/server/react-server/index.tsx
#	packages/use-intl/package.json
#	packages/use-intl/src/core/index.tsx
#	pnpm-lock.yaml
#	pnpm-workspace.yaml