Bun 1.4 adds experimental WebView for Puppeteer-free JSON API screenshots and JavaScript evaluation

Bun 1.4’s experimental Bun.WebView adds first-class browser automation to the runtime, removing the need for external tools like Puppeteer or Playwright. The feature supports either macOS WebKit or Chromium via Chrome DevTools Protocol, giving engineers a choice of backends. This integration is demonstrated by a 150-line TypeScript service that exposes endpoints for JavaScript execution and image capture, returning results as JSON. The approach creates a new browser tab per request, enabling concurrent operations while isolating state between calls.

The prototype’s memory footprint, 192MB to 256MB per request when running Chrome, suggests Bun.WebView is not yet optimized for high-density deployments. While this is lighter than spinning up a full Puppeteer instance, it still imposes a non-trivial cost for applications with many parallel requests. The trade-off is simplicity: engineers avoid managing separate browser processes or coordinating with external automation tools. However, the feature’s experimental status means stability and performance characteristics may change in future releases.

Bun.WebView’s JSON API design mirrors tools like shot-scraper but embeds the functionality directly into Bun’s runtime. This could simplify workflows for engineers who need occasional browser automation, such as scraping dynamic content or generating screenshots in CI pipelines. The lack of external dependencies reduces deployment complexity, but the feature’s reliance on Chrome DevTools Protocol may limit compatibility with non-Chromium browsers. Engineers should expect to handle edge cases like timeouts or rendering inconsistencies themselves, as Bun.WebView does not yet offer the robustness of mature automation suites.

The broader Bun 1.4 release also includes performance improvements, such as 5x lower idle CPU usage and 35% reduced memory consumption, alongside new utilities like Bun.Image and Bun.markdown. These changes suggest Bun is evolving into a more self-contained runtime, reducing reliance on external tools for common tasks. However, Bun.WebView’s experimental status means engineers should treat it as a preview rather than production-ready. Early adopters will need to monitor memory usage and stability, particularly in applications with unpredictable workloads or long-running browser sessions.