search

GoogleChromeLabs / carlo

Web rendering surface for Node applications
Apache License 2.0
9.31k stars 309 forks source link

How to keep Chrome and app’s Carlo synchronized? #17

Open pakastin opened 5 years ago

pakastin commented 5 years ago

I mean if user have (now or in the future) older or newer Chrome, what happens?

rkistner commented 5 years ago

I'm also interested in this. Breaking changes in DOM/JS APIs are fairly rare, so that's not my biggest concern. However, in my experience the DevTools protocol has major breaking changes every couple of Chrome versions. Puppeteer is tied to specific Chromium revisions for this reason, and ChromeDriver seems to claim compatiblity with 3 Chrome versions for each ChromeDriver version at most.

Is there a plan to be more "future-proof" with Carlo?

pakastin commented 5 years ago

How big is Carlo, would it be possible to package multiple versions if there’s a breaking change? Or somehow abstract dev tools API so that it’s backwards-compatible, at least for some while and with deprecation notices..

I’d need this in such a mission-critical application (digital signage), that would be nice to have this solved.

Electron has been quite unstable, especially v3 – would be happy to try Carlo out, since Puppeteer have been great in server-side.

pakastin commented 5 years ago

Or would it be possible to define certain Chrome version as dependency (at least in Linux)? I’ve seen that packages install other packages, but can they be defined to certain versions?

pakastin commented 5 years ago

Hmm..or was it so, that old versions of Chrome are not available? 🤔

styfle commented 5 years ago

How big is Carlo

Carlo is about 2 MB.

In contrast, Electron is about 130 MB.