Move chrome-aws-lambda to peerDependencies
·
16 commits
to main
since this release
BREAKING CHANGE: From now on, next-api-og-image has chrome-aws-lambda in peerDependencies... but what does it mean?
When installing next-api-og-image >= 4.0.0 you also have to install appropriate chrome-aws-lambda version.
In most cases, the
npm i next-api-og-image chrome-aws-lambda
# or
yarn add next-api-og-image chrome-aws-lambdawill be sufficient.
But when you'll encounter serverless function size exceed limit on Vercel:
npm i next-api-og-image chrome-aws-lambda@6.0.0
# or
yarn add next-api-og-image chrome-aws-lambda@6.0.0The 6.0.0 version of chrome-aws-lambda is smaller than the latest one (10.1.0 at the time of writing this release notes)
Acknowledgements
Gargantuan thanks to @transitive-bullshit for making research on this 🙏🏻
Full Changelog: 3.0.0...4.0.1
Contributors
transitive-bullshit