github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
a614bc45aa
puppeteer/utils/browser
History
Jack Franklin 0bcc5a7ad8
chore: migrate remaining tests to Mocha (#5616) 
This commit updates all the non-Puppeteer unit tests to run using Mocha and then deletes the custom test runner framework from this repository. The documentation has also been updated.
2020-04-09 20:12:32 +02:00
..
browser.spec.js chore: migrate remaining tests to Mocha (#5616) 2020-04-09 20:12:32 +02:00
README.md chore: update URLs (#5185) 2019-11-26 13:12:25 +01:00
WebSocket.js chore: make sure Puppeteer bundling works (#3239) 2018-09-13 20:08:51 +01:00

README.md

Bundling For Web Browsers

To bundle Puppeteer using Browserify:

  1. Clone Puppeteer repository: git clone https://github.com/puppeteer/puppeteer && cd puppeteer
  2. npm install
  3. Run npm run bundle

This will create ./utils/browser/puppeteer-web.js file that contains Puppeteer bundle.

You can use it later on in your web page to drive another browser instance through its WS Endpoint:

<script src='./puppeteer-web.js'></script>
<script>
  const puppeteer = require('puppeteer');
  const browser = await puppeteer.connect({
    browserWSEndpoint: '<another-browser-ws-endpont>'
  });
  // ... drive automation ...
</script>

See our puppeteer-web tests for details.

Running inside Chrome Extension

You might want to enable unsafe-eval inside the extension by adding the following to your manifest.json file:

"content_security_policy": "script-src 'self' 'unsafe-eval'; object-src 'self'"

Please see discussion in https://github.com/puppeteer/puppeteer/issues/3455.