8aa9a52c36
### Issue When the og module is a shared module being imported in both page and metadata image routes, it will be shared in the module graph. Especially in the edge runtime, since the `default` export is being used in the metadata image routes, then it can't be easily tree-shaked out. ### Solution Separate the image route to a separate layer which won't share modules with the page, so that image route is always bundling separately and the `@vercel/og` module only stays inside in that layer, when import image metadata named exports (size / alt / etc..) it can be still tree shaked. Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| app | ||
| index.test.ts | ||
| next.config.js | ||