archive/rsnext - DevGit

archive/rsnext

2 lines

60 B

JavaScript

Raw Normal View History

Move ImageResponse to next/og (#56662) ### Story Since we introduced `ImageResponse` into `next/server` export, there're a few libraries relying on `next/server` that accidentally ended up with bundling og image into the bundle. As og package is quite large that could easily raise the size concern for middleware, edge runtime routes. ### Struggles We've done optimizations. The tree-shaking strategies are tricky, we tried modularize imports and also optimize cjs require/exports to make sure you're not including og package into bundle if it's not being used. However, it's still not 100% can handle all the bundle optimization cases, such as `import {..} from "next/server.js"` could also ended up with the cjs bundle that failed the tree-shaking. ### Move on So we decide to move og `ImageResponse` into a separate export `next/og` Closes NEXT-1660

2023-10-19 16:26:48 +02:00

module.exports = require('./dist/server/og/image-response')