Comment by minimaxir
1 day ago
I have been building/vibecoding a similar tool and unfortunately came to the conclusion that in practice, there are just too many features dependent on the full Chrome stack that it's just more pragmatic to use a real Chromium installation despite the file size. Performance/image generation speed is still fine, though.
In Rust, the chromiumoxide crate is a performant way to interface with it for screenshots: https://crates.io/crates/chromiumoxide
> there are just too many features dependent on the full Chrome stack
Do you mind elaborating on what features are missing?
I think you could in theory have a similar webkit-based stripped down headless crate that might have a good tradeoff of features, performance, and size.