Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Suggestion: move chrome-aws-lambda to peer dependency

See original GitHub issue

Since the most recent version of chrome-aws-lambda is 49.7 MB, it leaves almost no room for additional client libs in the vercel lambda.

I’ve been running into this issue and it’s really frustrating.

So my proposal is to switch chrome-aws-lambda to be a peer dependency and allow the user of this library to choose which chrome version they want to use.

See my other comment here for the savings we’re talking about: https://github.com/neg4n/next-api-og-image/issues/23#issuecomment-1090319079

This would require also making puppeteer-core a peer dependency, since the two versions need to match up.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

neg4ncommented, Apr 11, 2022

https://github.com/neg4n/next-api-og-image/releases/tag/4.0.1

1reaction

neg4ncommented, Apr 8, 2022

Thanks @transitive-bullshit for your research regarding this topic 🤟🏻 Your suggestion about switching these dependencies to peerDependencies seems very sensible to me. I’ll investigate the topic as well and apply the changes during this weekend 🚀