OpenGraphMetadata type is weird

[lnuvy]

Link to the code that reproduces this issue

https://github.com/lnuvy/opengraph-error

To Reproduce

1. Cloning the above github project
2. Go to /post/[postId] page
3. You will see the r.map is not a function error

Current vs. Expected behavior

Common emails in type OpenGraphMetadata are colliding when type is an "article"

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:31:00 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6020
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Metadata (metadata, generateMetadata, next/head)

Which stage(s) are affected? (Select all that apply)

next dev (local), Other (Deployed)

Additional context

According to the type of built-in openGraph in next.js, when the openGraph type is "article", it doesn't matter if you put an email property.

However, r.map is not a function Error occurs due to emails properties when type is not a "website" type.

I found that the same problem occurred in the AWS deployment environment of the other project, as well as in the local area, and the page was not drawn.

I've built a similar environment on the link above. Thank you!

[devjiwonchoi]

Hi, please do try using a string[] type for emails. Also, please note that using implicit types from next/dist is not recommended.

emails: ['test']

EDIT: I'd recommend using it like:

type OpenGraph = Metadata['openGraph'];

EDIT2:

@lnuvy Hi, I found out that it was a bug and opened a PR for it. Thanks for bringing this up!

[lnuvy]

@devjiwonchoi Hi, I checked your PR now.
I wanted to open PR myself, but I didn't know how to solve it, so I left it on the issue.
Thank you for solving it. It was a good study for me, too 😃

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.