You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/01_bug_report.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -23,11 +23,11 @@ body:
23
23
attributes:
24
24
label: Verifications
25
25
options:
26
-
- label: I've verified that the problem I'm experiencing isn't covered in [the docs](https://next-intl-docs.vercel.app/).
26
+
- label: I've verified that the problem I'm experiencing isn't covered in [the docs](https://next-intl.dev).
27
27
required: true
28
28
- label: I've searched for similar, existing issues on [GitHub](https://github.com/amannn/next-intl/issues) and [Stack Overflow](https://stackoverflow.com/search?q=next-intl).
29
29
required: true
30
-
- label: I've compared my app to [a working example](https://next-intl-docs.vercel.app/examples) to look for differences.
30
+
- label: I've compared my app to [a working example](https://next-intl.dev/examples) to look for differences.
Copy file name to clipboardExpand all lines: examples/example-app-router-without-i18n-routing/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# example-app-router-without-i18n-routing
2
2
3
-
An example that showcases how an app can provide a locale in `i18n.ts` to `next-intl` in an App Router setup ([without i18n routing setup](https://next-intl-docs.vercel.app/docs/getting-started/app-router/without-i18n-routing)).
3
+
An example that showcases how an app can provide a locale in `i18n.ts` to `next-intl` in an App Router setup ([without i18n routing setup](https://next-intl.dev/docs/getting-started/app-router/without-i18n-routing)).
@@ -181,15 +181,15 @@ export default function createSharedNavigationFns<
181
181
: {
182
182
/**
183
183
* In case you're using `localePrefix: 'as-needed'` in combination with `domains`, the `defaultLocale` can differ by domain and therefore the locales that need to be prefixed can differ as well. For this particular case, this parameter should be provided in order to compute the correct pathname. Note that the actual domain is not part of the result, but only the pathname is returned.
Copy file name to clipboardExpand all lines: packages/next-intl/src/navigation/shared/utils.tsx
+1-1
Original file line number
Diff line number
Diff line change
@@ -273,7 +273,7 @@ export function applyPathnamePrefix<
273
273
}elseif(process.env.NODE_ENV!=='production'){
274
274
if(!domain){
275
275
console.error(
276
-
"You're using a routing configuration with `localePrefix: 'as-needed'` in combination with `domains`. In order to compute a correct pathname, you need to provide a `domain` parameter.\n\nSee: https://next-intl-docs.vercel.app/docs/routing#domains-localeprefix-asneeded"
276
+
"You're using a routing configuration with `localePrefix: 'as-needed'` in combination with `domains`. In order to compute a correct pathname, you need to provide a `domain` parameter.\n\nSee: https://next-intl.dev/docs/routing#domains-localeprefix-asneeded"
277
277
);
278
278
}else{
279
279
// If a domain was provided, but it wasn't found in the routing
Copy file name to clipboardExpand all lines: packages/next-intl/src/plugin.tsx
+2-2
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ function resolveI18nPath(providedPath?: string, cwd?: string) {
51
51
if(pathExists(candidate)){
52
52
if(!hasWarnedForDeprecatedI18nConfig){
53
53
console.warn(
54
-
`\n[next-intl] Reading request configuration from ${candidate} is deprecated, please see https://next-intl-docs.vercel.app/blog/next-intl-3-22#i18n-request — you can either move your configuration to ./i18n/request.ts or provide a custom path in your Next.js config:
54
+
`\n[next-intl] Reading request configuration from ${candidate} is deprecated, please see https://next-intl.dev/blog/next-intl-3-22#i18n-request — you can either move your configuration to ./i18n/request.ts or provide a custom path in your Next.js config:
"\n[next-intl] An `i18n` property was found in your Next.js config. This likely causes conflicts and should therefore be removed if you use the App Router.\n\nIf you're in progress of migrating from the Pages Router, you can refer to this example: https://next-intl-docs.vercel.app/examples#app-router-migration\n"
81
+
"\n[next-intl] An `i18n` property was found in your Next.js config. This likely causes conflicts and should therefore be removed if you use the App Router.\n\nIf you're in progress of migrating from the Pages Router, you can refer to this example: https://next-intl.dev/examples#app-router-migration\n"
Copy file name to clipboardExpand all lines: packages/next-intl/src/react-server/useConfig.tsx
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ function useHook<Value>(hookName: string, promise: Promise<Value>) {
10
10
error.message.includes("Cannot read properties of null (reading 'use')")
11
11
){
12
12
thrownewError(
13
-
`\`${hookName}\` is not callable within an async component. Please refer to https://next-intl-docs.vercel.app/docs/environments/server-client-components#async-components`,
13
+
`\`${hookName}\` is not callable within an async component. Please refer to https://next-intl.dev/docs/environments/server-client-components#async-components`,
* Sets the `Link` response header to notify search engines about content in other languages (defaults to `true`). See https://developers.google.com/search/docs/specialty/international/localized-versions#http
'Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering',
27
+
'Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `setRequestLocale` API to enable static rendering, see https://next-intl.dev/docs/getting-started/app-router/with-i18n-routing#static-rendering',
Copy file name to clipboardExpand all lines: packages/next-intl/src/server/react-server/RequestLocaleLegacy.tsx
+2-2
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ function getLocaleFromHeaderImpl() {
22
22
(errorasany).digest==='DYNAMIC_SERVER_USAGE'
23
23
){
24
24
thrownewError(
25
-
'Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering',
25
+
'Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `setRequestLocale` API to enable static rendering, see https://next-intl.dev/docs/getting-started/app-router/with-i18n-routing#static-rendering',
26
26
{cause: error}
27
27
);
28
28
}else{
@@ -33,7 +33,7 @@ function getLocaleFromHeaderImpl() {
33
33
if(!locale){
34
34
if(process.env.NODE_ENV!=='production'){
35
35
console.error(
36
-
`\nUnable to find \`next-intl\` locale because the middleware didn't run on this request. See https://next-intl-docs.vercel.app/docs/routing/middleware#unable-to-find-locale. The \`notFound()\` function will be called as a result.\n`
36
+
`\nUnable to find \`next-intl\` locale because the middleware didn't run on this request. See https://next-intl.dev/docs/routing/middleware#unable-to-find-locale. The \`notFound()\` function will be called as a result.\n`
0 commit comments