rsnext/test/e2e/app-dir/metadata-dynamic-routes/app
Jiachi Liu 6f30c911d6
Prefer to use deployment url for metadata routes on production (#48556)
Use should only need to configure one `metadataBase` as fixed domain or
url but metadata image routes can still work properly with `VERCEL_URL`
in preview deployments

If you configured `new URL('https://mydomain.com')`, it will work for
canonical url all the time since it's for SEO.
For preview deployments metadata image routes will work with deployment
url as they're always bound with deployment.
For production deployments metadata images routes can be alias to the
configured `metadataBase` as they could be the expected exposed domain

Follow up for #47910

link NEXT-887
2023-04-19 10:26:08 +00:00
..
(group) feat: generate image metadata (#48362) 2023-04-14 20:52:31 +00:00
apple-icon.tsx Vendor @vercel/og and expose ImageResponse (#47715) 2023-03-31 02:29:10 +00:00
favicon.tsx Skip favicon.js for metadata (#47790) 2023-04-02 01:35:24 +02:00
icon.tsx Vendor @vercel/og and expose ImageResponse (#47715) 2023-03-31 02:29:10 +00:00
layout.tsx Prefer to use deployment url for metadata routes on production (#48556) 2023-04-19 10:26:08 +00:00
manifest.ts Update MetadataRoute to namespace (#47674) 2023-03-30 15:27:44 -07:00
opengraph-image.tsx Vendor @vercel/og and expose ImageResponse (#47715) 2023-03-31 02:29:10 +00:00
page.tsx Provide default metadataBase for local and vercel deployment (#47568) 2023-03-30 16:27:24 -07:00
robots.ts Update MetadataRoute to namespace (#47674) 2023-03-30 15:27:44 -07:00
sitemap.ts Update MetadataRoute to namespace (#47674) 2023-03-30 15:27:44 -07:00
twitter-image.tsx Vendor @vercel/og and expose ImageResponse (#47715) 2023-03-31 02:29:10 +00:00