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

…#1655)

Ref: https://x.com/ddunderfelt/status/1874403640515121642

…1665)"

This reverts commit 32fc4e3.

…-plugin-import` (#1667)

@amannn Following our conversation on X, these are the changes that I've
made that appear to be fixing the imports when the `import/named` ESLint
rule is used.

As mentioned before, I also took the liberty of adding the ESLint rule
`'import/extensions': 'error'` to ensure the right extensions are used
in the import/export statements. For context, when compiling to ESM
modules, TS copies over the import/export statements as-is, so during
development, runtime compatible file extensions must be used.

For local testing I ran a build and then manually copied over the `dist`
folder into `node_modules/next-intl` in my other project.

…der (#1679)

([ref](#1631 (comment)))