This is useful but it uses precompiled binaries of chromium that run in a lambda. I didn't find the repo for re-creating them from source. Seems like one of those things that doesn't need a pre-compiled binary it needs instructions for how the binary was built so I don't have to trust some third party chromium distribution.
Does Vercel charge for the compute duration in addition to the number of requests for Next.js apps? I see they charge for Function Duration (https://vercel.com/docs/pricing/serverless-functions#managin...) but I am unsure if Next.js apps are considered as Vercel Functions.
Comments
This is useful but it uses precompiled binaries of chromium that run in a lambda. I didn't find the repo for re-creating them from source. Seems like one of those things that doesn't need a pre-compiled binary it needs instructions for how the binary was built so I don't have to trust some third party chromium distribution.
I went to their org and thought, "well there's the repo right there," but you're right, it's just a README with a link to binaries. https://github.com/chromium-for-lambda/chromium-binaries
Started to make sense when I checked the website and their business model is charging for updated Chrome binaries: https://pro.chromiumforlambda.org/
Does Vercel charge for the compute duration in addition to the number of requests for Next.js apps? I see they charge for Function Duration (https://vercel.com/docs/pricing/serverless-functions#managin...) but I am unsure if Next.js apps are considered as Vercel Functions.
Nice, is it headless or headful?
Looks like puppeteer running headless
https://github.com/chromium-for-lambda/chromium-on-vercel/bl...