use import type to import from 'next' in ts examples (#53568)

Updates typescript examples in https://nextjs.org/docs/app/building-your-application/optimizing/metadata#static-metadata to use `import type` instead of `import`. ![CleanShot 2023-08-04 at 17 28 12](https://github.com/vercel/next.js/assets/179761/d14503a4-1453-4f8f-95de-9d40ad1917ef)
vercel · Aug 4, 2023 · aac4d9c · aac4d9c
1 parent 49d4f8a
commit aac4d9c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/02-app/01-building-your-application/06-optimizing/04-metadata.mdx b/docs/02-app/01-building-your-application/06-optimizing/04-metadata.mdx
@@ -22,7 +22,7 @@ With both these options, Next.js will automatically generate the relevant `<head
 To define static metadata, export a [`Metadata` object](/docs/app/api-reference/functions/generate-metadata#metadata-object) from a `layout.js` or static `page.js` file.
 
 ```tsx filename="layout.tsx / page.tsx" switcher
-import { Metadata } from 'next'
+import type { Metadata } from 'next'
 
 export const metadata: Metadata = {
   title: '...',
@@ -48,7 +48,7 @@ For all the available options, see the [API Reference](/docs/app/api-reference/f
 You can use `generateMetadata` function to `fetch` metadata that requires dynamic values.
 
 ```tsx filename="app/products/[id]/page.tsx" switcher
-import { Metadata, ResolvingMetadata } from 'next'
+import type { Metadata, ResolvingMetadata } from 'next'
 
 type Props = {
   params: { id: string }