-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add puppeteer to whitelist #41
Comments
Adding So I'll probably drop this ticket soon. |
An update on this:
Puppeteer currently uses Chromium revision Chromium prebuilt links: |
I've changed my mind, will try to replace Check this comment for details: #51 (comment) |
I've changed my mind again, we can't reproduce the |
I would love to make
puppeteer
available to add-on devs, instead of the horrible littlephantomjs
module that is currently available.I'll just write my thoughts about this here until I get to a point where this is actually doable.
Why move away from
phantomjs
?polyfill
is set totrue
Why did we even use it in the first place then?
phantomjs
binary is 40-50mb, while the bundledchromium
ofpuppeteer
is a staggering 300mbWhat would be the solution to this mess?
The solution would be to use prebuilt
chromium
binaries that were built withheadless_shell
. This would (hopefully) drastically reduce it's size.But
puppeteer
has no setting to getheadless_shell
prebuilts, and buildingchromium
myself for all OSs would most probably be a hellish task, not to mention the fact that it would not be trustworthy, it should be gotten from an official source.One issue thread seems to suggest there are official
headless_shell
builds, example:https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/583214/headless-shell.zip
Related issues on
puppeteer
:puppeteer/puppeteer#3155
puppeteer/puppeteer#3140
puppeteer/puppeteer#3027
puppeteer/puppeteer#500
The text was updated successfully, but these errors were encountered: