However, Chromium still has some dependency on Google web services and binaries. Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. In scenarios where the objectives conflict, the objective of higher significance should take precedence. However, almost all of these features must be manually activated or enabled. ungoogled-chromium features tweaks to enhance privacy, control, and transparency.Unlike other Chromium forks that have their own visions of a web browser, ungoogled-chromium is essentially a drop-in replacement for Chromium. ungoogled-chromium retains the default Chromium experience as closely as possible.ungoogled-chromium is Google Chromium, sans dependency on Google web services.In descending order of significance (i.e. Help is welcome! See the docs/contributing.md document for more information. The problem is I haven't found any Puppeteer configuration I can use for such purpose.A lightweight approach to removing Google web service dependency Force my users to download Chromium at runtime (at first usage for example).Download Chromium selectively at packaging time (still on dev machine).Download all-platform Chromium when npm install (on dev machine).I should be able to do one of the following: Being current platform Linux, this very version of Chromium is then shipped regardlessly on every platform's app.
The problem is: Chromium is downloaded at npm install time, and it's done selectively based on the current platform. It works nice-and-smooth except for this issue:Ĭhromium is not downloaded exception is thrown when the app is executed on a platform different than the one the app has been packaged on.īetter said, I'm developing on a Linux environment and I'm packaging my app for both Linux and Windows, Linux app works fine, Windows app doesn't. I'm building a UI-automator with Puppeteer and I'm shipping it as a Electron-packaged app.
0 kommentar(er)
