next/og doesn't seem to except woff while satori does?
Unanswered
Saarloos Wolfdog posted this in #help-forum
Saarloos WolfdogOP
Isn't next/og just using satori under the hood? When we use woff we get ...
[cause]: Error: Unsupported OpenType signature expo
at Object.parseBuffer [as parse] (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:12835:15)
at zt.addFonts (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:21759:58)
at new zt (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:21735:14)
at xl (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:23553:65)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async render (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:25420:17)
at async Object.start (webpack-internal:///(rsc)/../../../node_modules/.pnpm/next@14.0.3_@babel+core@7.22.9_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/@vercel/og/index.edge.js:25456:33)
}