fix: metadatabase warning message (#52363)

This PR is a small grammar change to the warning message since "fallbacks to" is not grammatically correct.
vercel · Jul 7, 2023 · 2721714 · 2721714
1 parent 2c12c6a
commit 2721714
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/packages/next/src/lib/metadata/resolvers/resolve-url.ts b/packages/next/src/lib/metadata/resolvers/resolve-url.ts
@@ -33,7 +33,7 @@ export function getSocialImageFallbackMetadataBase(
 
   if (isMetadataBaseMissing) {
     Log.warnOnce(
-      `\nmetadata.metadataBase is not set for resolving social open graph or twitter images, fallbacks to "${fallbackMetadata.origin}". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase`
+      `\nmetadata.metadataBase is not set for resolving social open graph or twitter images, using "${fallbackMetadata.origin}". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase`
     )
   }
 

diff --git a/test/e2e/app-dir/metadata-missing-metadata-base/index.test.ts b/test/e2e/app-dir/metadata-missing-metadata-base/index.test.ts
@@ -24,7 +24,7 @@ describe('app dir - metadata missing metadataBase', () => {
     await next.start()
     await fetchViaHTTP(next.url, '/')
     expect(next.cliOutput).toInclude(
-      'metadata.metadataBase is not set for resolving social open graph or twitter images, fallbacks to'
+      'metadata.metadataBase is not set for resolving social open graph or twitter images, using'
     )
     expect(next.cliOutput).toInclude(`"http://localhost:${port}`)
     expect(next.cliOutput).toInclude(