RubyGems - isomorfeus-puppetmaster - Versions diffs - 0.5.6 → 0.6.2 - Mend

isomorfeus-puppetmaster 0.5.6 → 0.6.2

Files changed (979) hide show

data/node_modules/puppeteer-core/README.md DELETED Viewed

@@ -1,481 +0,0 @@
-# Puppeteer
-<!-- [START badges] -->
-[![Build status](https://github.com/puppeteer/puppeteer/workflows/run-checks/badge.svg)](https://github.com/puppeteer/puppeteer/actions?query=workflow%3Arun-checks) [![npm puppeteer package](https://img.shields.io/npm/v/puppeteer.svg)](https://npmjs.org/package/puppeteer)
-<!-- [END badges] -->
-<img src="https://user-images.githubusercontent.com/10379601/29446482-04f7036a-841f-11e7-9872-91d1fc2ea683.png" height="200" align="right">
-###### [API](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md) | [FAQ](#faq) | [Contributing](https://github.com/puppeteer/puppeteer/blob/main/CONTRIBUTING.md) | [Troubleshooting](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md)
-> Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). Puppeteer runs [headless](https://developers.google.com/web/updates/2017/04/headless-chrome) by default, but can be configured to run full (non-headless) Chrome or Chromium.
-<!-- [START usecases] -->
-###### What can I do?
-Most things that you can do manually in the browser can be done using Puppeteer! Here are a few examples to get you started:
-- Generate screenshots and PDFs of pages.
-- Crawl a SPA (Single-Page Application) and generate pre-rendered content (i.e. "SSR" (Server-Side Rendering)).
-- Automate form submission, UI testing, keyboard input, etc.
-- Create an up-to-date, automated testing environment. Run your tests directly in the latest version of Chrome using the latest JavaScript and browser features.
-- Capture a [timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference) of your site to help diagnose performance issues.
-- Test Chrome Extensions.
-<!-- [END usecases] -->
-<!-- [START getstarted] -->
-## Getting Started
-### Installation
-To use Puppeteer in your project, run:
-```bash
-npm i puppeteer
-# or "yarn add puppeteer"
-```
-Note: When you install Puppeteer, it downloads a recent version of Chromium (~170MB Mac, ~282MB Linux, ~280MB Win) that is guaranteed to work with the API. To skip the download, download into another path, or download a different browser, see [Environment variables](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#environment-variables).
-### puppeteer-core
-Since version 1.7.0 we publish the [`puppeteer-core`](https://www.npmjs.com/package/puppeteer-core) package,
-a version of Puppeteer that doesn't download any browser by default.
-```bash
-npm i puppeteer-core
-# or "yarn add puppeteer-core"
-```
-`puppeteer-core` is intended to be a lightweight version of Puppeteer for launching an existing browser installation or for connecting to a remote one. Be sure that the version of puppeteer-core you install is compatible with the
-browser you intend to connect to.
-See [puppeteer vs puppeteer-core](https://github.com/puppeteer/puppeteer/blob/main/docs/api.md#puppeteer-vs-puppeteer-core).
-### Usage
-Puppeteer follows the latest [maintenance LTS](https://github.com/nodejs/Release#release-schedule) version of Node.
-Note: Prior to v1.18.1, Puppeteer required at least Node v6.4.0. Versions from v1.18.1 to v2.1.0 rely on
-Node 8.9.0+. Starting from v3.0.0 Puppeteer starts to rely on Node 10.18.1+. All examples below use async/await which is only supported in Node v7.6.0 or greater.
-Puppeteer will be familiar to people using other browser testing frameworks. You create an instance
-of `Browser`, open pages, and then manipulate them with [Puppeteer's API](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#).
-**Example** - navigating to https://example.com and saving a screenshot as _example.png_:
-Save file as **example.js**
-```js
-const puppeteer = require('puppeteer');
-(async () => {
-  const browser = await puppeteer.launch();
-  const page = await browser.newPage();
-  await page.goto('https://example.com');
-  await page.screenshot({ path: 'example.png' });
-  await browser.close();
-})();
-```
-Execute script on the command line
-```bash
-node example.js
-```
-Puppeteer sets an initial page size to 800×600px, which defines the screenshot size. The page size can be customized with [`Page.setViewport()`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#pagesetviewportviewport).
-**Example** - create a PDF.
-Save file as **hn.js**
-```js
-const puppeteer = require('puppeteer');
-(async () => {
-  const browser = await puppeteer.launch();
-  const page = await browser.newPage();
-  await page.goto('https://news.ycombinator.com', {
-    waitUntil: 'networkidle2',
-  });
-  await page.pdf({ path: 'hn.pdf', format: 'a4' });
-  await browser.close();
-})();
-```
-Execute script on the command line
-```bash
-node hn.js
-```
-See [`Page.pdf()`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#pagepdfoptions) for more information about creating pdfs.
-**Example** - evaluate script in the context of the page
-Save file as **get-dimensions.js**
-```js
-const puppeteer = require('puppeteer');
-(async () => {
-  const browser = await puppeteer.launch();
-  const page = await browser.newPage();
-  await page.goto('https://example.com');
-  // Get the "viewport" of the page, as reported by the page.
-  const dimensions = await page.evaluate(() => {
-    return {
-      width: document.documentElement.clientWidth,
-      height: document.documentElement.clientHeight,
-      deviceScaleFactor: window.devicePixelRatio,
-    };
-  });
-  console.log('Dimensions:', dimensions);
-  await browser.close();
-})();
-```
-Execute script on the command line
-```bash
-node get-dimensions.js
-```
-See [`Page.evaluate()`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#pageevaluatepagefunction-args) for more information on `evaluate` and related methods like `evaluateOnNewDocument` and `exposeFunction`.
-<!-- [END getstarted] -->
-<!-- [START runtimesettings] -->
-## Default runtime settings
-**1. Uses Headless mode**
-Puppeteer launches Chromium in [headless mode](https://developers.google.com/web/updates/2017/04/headless-chrome). To launch a full version of Chromium, set the [`headless` option](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#puppeteerlaunchoptions) when launching a browser:
-```js
-const browser = await puppeteer.launch({ headless: false }); // default is true
-```
-**2. Runs a bundled version of Chromium**
-By default, Puppeteer downloads and uses a specific version of Chromium so its API
-is guaranteed to work out of the box. To use Puppeteer with a different version of Chrome or Chromium,
-pass in the executable's path when creating a `Browser` instance:
-```js
-const browser = await puppeteer.launch({ executablePath: '/path/to/Chrome' });
-```
-You can also use Puppeteer with Firefox Nightly (experimental support). See [`Puppeteer.launch()`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#puppeteerlaunchoptions) for more information.
-See [`this article`](https://www.howtogeek.com/202825/what%E2%80%99s-the-difference-between-chromium-and-chrome/) for a description of the differences between Chromium and Chrome. [`This article`](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/chromium_browser_vs_google_chrome.md) describes some differences for Linux users.
-**3. Creates a fresh user profile**
-Puppeteer creates its own browser user profile which it **cleans up on every run**.
-<!-- [END runtimesettings] -->
-## Resources
-- [API Documentation](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md)
-- [Examples](https://github.com/puppeteer/puppeteer/tree/main/examples/)
-- [Community list of Puppeteer resources](https://github.com/transitive-bullshit/awesome-puppeteer)
-<!-- [START debugging] -->
-## Debugging tips
-1.  Turn off headless mode - sometimes it's useful to see what the browser is
-    displaying. Instead of launching in headless mode, launch a full version of
-    the browser using `headless: false`:
-    ```js
-    const browser = await puppeteer.launch({ headless: false });
-    ```
-2.  Slow it down - the `slowMo` option slows down Puppeteer operations by the
-    specified amount of milliseconds. It's another way to help see what's going on.
-    ```js
-    const browser = await puppeteer.launch({
-      headless: false,
-      slowMo: 250, // slow down by 250ms
-    });
-    ```
-3.  Capture console output - You can listen for the `console` event.
-    This is also handy when debugging code in `page.evaluate()`:
-    ```js
-    page.on('console', (msg) => console.log('PAGE LOG:', msg.text()));
-    await page.evaluate(() => console.log(`url is ${location.href}`));
-    ```
-4.  Use debugger in application code browser
-    There are two execution context: node.js that is running test code, and the browser
-    running application code being tested. This lets you debug code in the
-    application code browser; ie code inside `evaluate()`.
-    - Use `{devtools: true}` when launching Puppeteer:
-      ```js
-      const browser = await puppeteer.launch({ devtools: true });
-      ```
-    - Change default test timeout:
-      jest: `jest.setTimeout(100000);`
-      jasmine: `jasmine.DEFAULT_TIMEOUT_INTERVAL = 100000;`
-      mocha: `this.timeout(100000);` (don't forget to change test to use [function and not '=>'](https://stackoverflow.com/a/23492442))
-    - Add an evaluate statement with `debugger` inside / add `debugger` to an existing evaluate statement:
-      ```js
-      await page.evaluate(() => {
-        debugger;
-      });
-      ```
-      The test will now stop executing in the above evaluate statement, and chromium will stop in debug mode.
-5.  Use debugger in node.js
-    This will let you debug test code. For example, you can step over `await page.click()` in the node.js script and see the click happen in the application code browser.
-    Note that you won't be able to run `await page.click()` in
-    DevTools console due to this [Chromium bug](https://bugs.chromium.org/p/chromium/issues/detail?id=833928). So if
-    you want to try something out, you have to add it to your test file.
-    - Add `debugger;` to your test, eg:
-      ```js
-      debugger;
-      await page.click('a[target=_blank]');
-      ```
-    - Set `headless` to `false`
-    - Run `node --inspect-brk`, eg `node --inspect-brk node_modules/.bin/jest tests`
-    - In Chrome open `chrome://inspect/#devices` and click `inspect`
-    - In the newly opened test browser, type `F8` to resume test execution
-    - Now your `debugger` will be hit and you can debug in the test browser
-6.  Enable verbose logging - internal DevTools protocol traffic
-    will be logged via the [`debug`](https://github.com/visionmedia/debug) module under the `puppeteer` namespace.
-         # Basic verbose logging
-         env DEBUG="puppeteer:*" node script.js
-         # Protocol traffic can be rather noisy. This example filters out all Network domain messages
-         env DEBUG="puppeteer:*" env DEBUG_COLORS=true node script.js 2>&1 | grep -v '"Network'
-7.  Debug your Puppeteer (node) code easily, using [ndb](https://github.com/GoogleChromeLabs/ndb)
-- `npm install -g ndb` (or even better, use [npx](https://github.com/zkat/npx)!)
-- add a `debugger` to your Puppeteer (node) code
-- add `ndb` (or `npx ndb`) before your test command. For example:
-  `ndb jest` or `ndb mocha` (or `npx ndb jest` / `npx ndb mocha`)
-- debug your test inside chromium like a boss!
-<!-- [END debugging] -->
-<!-- [START typescript] -->
-## Usage with TypeScript
-We have recently completed a migration to move the Puppeteer source code from JavaScript to TypeScript and as of version 7.0.1 we ship our own built-in type definitions.
-If you are on a version older than 7, we recommend installing the Puppeteer type definitions from the [DefinitelyTyped](https://definitelytyped.org/) repository:
-```bash
-npm install --save-dev @types/puppeteer
-```
-The types that you'll see appearing in the Puppeteer source code are based off the great work of those who have contributed to the `@types/puppeteer` package. We really appreciate the hard work those people put in to providing high quality TypeScript definitions for Puppeteer's users.
-<!-- [END typescript] -->
-## Contributing to Puppeteer
-Check out [contributing guide](https://github.com/puppeteer/puppeteer/blob/main/CONTRIBUTING.md) to get an overview of Puppeteer development.
-<!-- [START faq] -->
-# FAQ
-#### Q: Who maintains Puppeteer?
-The Chrome DevTools team maintains the library, but we'd love your help and expertise on the project!
-See [Contributing](https://github.com/puppeteer/puppeteer/blob/main/CONTRIBUTING.md).
-#### Q: What is the status of cross-browser support?
-Official Firefox support is currently experimental. The ongoing collaboration with Mozilla aims to support common end-to-end testing use cases, for which developers expect cross-browser coverage. The Puppeteer team needs input from users to stabilize Firefox support and to bring missing APIs to our attention.
-From Puppeteer v2.1.0 onwards you can specify [`puppeteer.launch({product: 'firefox'})`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#puppeteerlaunchoptions) to run your Puppeteer scripts in Firefox Nightly, without any additional custom patches. While [an older experiment](https://www.npmjs.com/package/puppeteer-firefox) required a patched version of Firefox, [the current approach](https://wiki.mozilla.org/Remote) works with “stock” Firefox.
-We will continue to collaborate with other browser vendors to bring Puppeteer support to browsers such as Safari.
-This effort includes exploration of a standard for executing cross-browser commands (instead of relying on the non-standard DevTools Protocol used by Chrome).
-#### Q: What are Puppeteer’s goals and principles?
-The goals of the project are:
-- Provide a slim, canonical library that highlights the capabilities of the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/).
-- Provide a reference implementation for similar testing libraries. Eventually, these other frameworks could adopt Puppeteer as their foundational layer.
-- Grow the adoption of headless/automated browser testing.
-- Help dogfood new DevTools Protocol features...and catch bugs!
-- Learn more about the pain points of automated browser testing and help fill those gaps.
-We adapt [Chromium principles](https://www.chromium.org/developers/core-principles) to help us drive product decisions:
-- **Speed**: Puppeteer has almost zero performance overhead over an automated page.
-- **Security**: Puppeteer operates off-process with respect to Chromium, making it safe to automate potentially malicious pages.
-- **Stability**: Puppeteer should not be flaky and should not leak memory.
-- **Simplicity**: Puppeteer provides a high-level API that’s easy to use, understand, and debug.
-#### Q: Is Puppeteer replacing Selenium/WebDriver?
-**No**. Both projects are valuable for very different reasons:
-- Selenium/WebDriver focuses on cross-browser automation; its value proposition is a single standard API that works across all major browsers.
-- Puppeteer focuses on Chromium; its value proposition is richer functionality and higher reliability.
-That said, you **can** use Puppeteer to run tests against Chromium, e.g. using the community-driven [jest-puppeteer](https://github.com/smooth-code/jest-puppeteer). While this probably shouldn’t be your only testing solution, it does have a few good points compared to WebDriver:
-- Puppeteer requires zero setup and comes bundled with the Chromium version it works best with, making it [very easy to start with](https://github.com/puppeteer/puppeteer/#getting-started). At the end of the day, it’s better to have a few tests running chromium-only, than no tests at all.
-- Puppeteer has event-driven architecture, which removes a lot of potential flakiness. There’s no need for evil “sleep(1000)” calls in puppeteer scripts.
-- Puppeteer runs headless by default, which makes it fast to run. Puppeteer v1.5.0 also exposes browser contexts, making it possible to efficiently parallelize test execution.
-- Puppeteer shines when it comes to debugging: flip the “headless” bit to false, add “slowMo”, and you’ll see what the browser is doing. You can even open Chrome DevTools to inspect the test environment.
-#### Q: Why doesn’t Puppeteer v.XXX work with Chromium v.YYY?
-We see Puppeteer as an **indivisible entity** with Chromium. Each version of Puppeteer bundles a specific version of Chromium – **the only** version it is guaranteed to work with.
-This is not an artificial constraint: A lot of work on Puppeteer is actually taking place in the Chromium repository. Here’s a typical story:
-- A Puppeteer bug is reported: https://github.com/puppeteer/puppeteer/issues/2709
-- It turned out this is an issue with the DevTools protocol, so we’re fixing it in Chromium: https://chromium-review.googlesource.com/c/chromium/src/+/1102154
-- Once the upstream fix is landed, we roll updated Chromium into Puppeteer: https://github.com/puppeteer/puppeteer/pull/2769
-However, oftentimes it is desirable to use Puppeteer with the official Google Chrome rather than Chromium. For this to work, you should install a `puppeteer-core` version that corresponds to the Chrome version.
-For example, in order to drive Chrome 71 with puppeteer-core, use `chrome-71` npm tag:
-```bash
-npm install puppeteer-core@chrome-71
-```
-#### Q: Which Chromium version does Puppeteer use?
-Look for the `chromium` entry in [revisions.ts](https://github.com/puppeteer/puppeteer/blob/main/src/revisions.ts). To find the corresponding Chromium commit and version number, search for the revision prefixed by an `r` in [OmahaProxy](https://omahaproxy.appspot.com/)'s "Find Releases" section.
-#### Q: Which Firefox version does Puppeteer use?
-Since Firefox support is experimental, Puppeteer downloads the latest [Firefox Nightly](https://wiki.mozilla.org/Nightly) when the `PUPPETEER_PRODUCT` environment variable is set to `firefox`. That's also why the value of `firefox` in [revisions.ts](https://github.com/puppeteer/puppeteer/blob/main/src/revisions.ts) is `latest` -- Puppeteer isn't tied to a particular Firefox version.
-To fetch Firefox Nightly as part of Puppeteer installation:
-```bash
-PUPPETEER_PRODUCT=firefox npm i puppeteer
-# or "yarn add puppeteer"
-```
-#### Q: What’s considered a “Navigation”?
-From Puppeteer’s standpoint, **“navigation” is anything that changes a page’s URL**.
-Aside from regular navigation where the browser hits the network to fetch a new document from the web server, this includes [anchor navigations](https://www.w3.org/TR/html5/single-page.html#scroll-to-fragid) and [History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) usage.
-With this definition of “navigation,” **Puppeteer works seamlessly with single-page applications.**
-#### Q: What’s the difference between a “trusted" and "untrusted" input event?
-In browsers, input events could be divided into two big groups: trusted vs. untrusted.
-- **Trusted events**: events generated by users interacting with the page, e.g. using a mouse or keyboard.
-- **Untrusted event**: events generated by Web APIs, e.g. `document.createEvent` or `element.click()` methods.
-Websites can distinguish between these two groups:
-- using an [`Event.isTrusted`](https://developer.mozilla.org/en-US/docs/Web/API/Event/isTrusted) event flag
-- sniffing for accompanying events. For example, every trusted `'click'` event is preceded by `'mousedown'` and `'mouseup'` events.
-For automation purposes it’s important to generate trusted events. **All input events generated with Puppeteer are trusted and fire proper accompanying events.** If, for some reason, one needs an untrusted event, it’s always possible to hop into a page context with `page.evaluate` and generate a fake event:
-```js
-await page.evaluate(() => {
-  document.querySelector('button[type=submit]').click();
-});
-```
-#### Q: What features does Puppeteer not support?
-You may find that Puppeteer does not behave as expected when controlling pages that incorporate audio and video. (For example, [video playback/screenshots is likely to fail](https://github.com/puppeteer/puppeteer/issues/291).) There are two reasons for this:
-- Puppeteer is bundled with Chromium — not Chrome — and so by default, it inherits all of [Chromium's media-related limitations](https://www.chromium.org/audio-video). This means that Puppeteer does not support licensed formats such as AAC or H.264. (However, it is possible to force Puppeteer to use a separately-installed version Chrome instead of Chromium via the [`executablePath` option to `puppeteer.launch`](https://github.com/puppeteer/puppeteer/blob/v12.0.1/docs/api.md#puppeteerlaunchoptions). You should only use this configuration if you need an official release of Chrome that supports these media formats.)
-- Since Puppeteer (in all configurations) controls a desktop version of Chromium/Chrome, features that are only supported by the mobile version of Chrome are not supported. This means that Puppeteer [does not support HTTP Live Streaming (HLS)](https://caniuse.com/#feat=http-live-streaming).
-#### Q: I am having trouble installing / running Puppeteer in my test environment. Where should I look for help?
-We have a [troubleshooting](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md) guide for various operating systems that lists the required dependencies.
-#### Q: Chromium gets downloaded on every `npm ci` run. How can I cache the download?
-The default download path is `node_modules/puppeteer/.local-chromium`. However, you can change that path with the `PUPPETEER_DOWNLOAD_PATH` environment variable.
-Puppeteer uses that variable to resolve the Chromium executable location during launch, so you don’t need to specify `PUPPETEER_EXECUTABLE_PATH` as well.
-For example, if you wish to keep the Chromium download in `~/.npm/chromium`:
-```sh
-export PUPPETEER_DOWNLOAD_PATH=~/.npm/chromium
-npm ci
-# by default the Chromium executable path is inferred
-# from the download path
-npm test
-# a new run of npm ci will check for the existence of
-# Chromium in ~/.npm/chromium
-npm ci
-```
-#### Q: How do I try/test a prerelease version of Puppeteer?
-You can check out this repo or install the latest prerelease from npm:
-```bash
-npm i --save puppeteer@next
-```
-Please note that prerelease may be unstable and contain bugs.
-#### Q: I have more questions! Where do I ask?
-There are many ways to get help on Puppeteer:
-- [bugtracker](https://github.com/puppeteer/puppeteer/issues)
-- [Stack Overflow](https://stackoverflow.com/questions/tagged/puppeteer)
-Make sure to search these channels before posting your question.
-<!-- [END faq] -->

data/node_modules/puppeteer-core/cjs-entry-core.js DELETED Viewed

@@ -1,29 +0,0 @@
-/**
- * Copyright 2020 Google Inc. All rights reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-/**
- * We use `export default puppeteer` in `src/index.ts` to expose the library But
- * TypeScript in CJS mode compiles that to `exports.default = `. This means that
- * our CJS Node users would have to use `require('puppeteer').default` which
- * isn't very nice.
- *
- * So instead we expose this file as our entry point. This requires the compiled
- * Puppeteer output and re-exports the `default` export via `module.exports.`
- * This means that we can publish to CJS and ESM whilst maintaining the expected
- * import behaviour for CJS and ESM users.
- */
-const puppeteerExport = require('./lib/cjs/puppeteer/node-puppeteer-core');
-module.exports = puppeteerExport.default;

data/node_modules/puppeteer-core/cjs-entry.js DELETED Viewed

@@ -1,29 +0,0 @@
-/**
- * Copyright 2020 Google Inc. All rights reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-/**
- * We use `export default puppeteer` in `src/index.ts` to expose the library But
- * TypeScript in CJS mode compiles that to `exports.default = `. This means that
- * our CJS Node users would have to use `require('puppeteer').default` which
- * isn't very nice.
- *
- * So instead we expose this file as our entry point. This requires the compiled
- * Puppeteer output and re-exports the `default` export via `module.exports.`
- * This means that we can publish to CJS and ESM whilst maintaining the expected
- * import behaviour for CJS and ESM users.
- */
-const puppeteerExport = require('./lib/cjs/puppeteer/node');
-module.exports = puppeteerExport.default;

data/node_modules/puppeteer-core/install.js DELETED Viewed

@@ -1,89 +0,0 @@
-/**
- * Copyright 2017 Google Inc. All rights reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-/**
- * This file is part of public API.
- *
- * By default, the `puppeteer` package runs this script during the installation
- * process unless one of the env flags is provided.
- * `puppeteer-core` package doesn't include this step at all. However, it's
- * still possible to install a supported browser using this script when
- * necessary.
- */
-const compileTypeScriptIfRequired = require('./typescript-if-required');
-async function download() {
-  await compileTypeScriptIfRequired();
-  // need to ensure TS is compiled before loading the installer
-  const {
-    downloadBrowser,
-    logPolitely,
-  } = require('./lib/cjs/puppeteer/node/install');
-  if (process.env.PUPPETEER_SKIP_DOWNLOAD) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_DOWNLOAD" environment variable was found.'
-    );
-    return;
-  }
-  if (
-    process.env.NPM_CONFIG_PUPPETEER_SKIP_DOWNLOAD ||
-    process.env.npm_config_puppeteer_skip_download
-  ) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_DOWNLOAD" was set in npm config.'
-    );
-    return;
-  }
-  if (
-    process.env.NPM_PACKAGE_CONFIG_PUPPETEER_SKIP_DOWNLOAD ||
-    process.env.npm_package_config_puppeteer_skip_download
-  ) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_DOWNLOAD" was set in project config.'
-    );
-    return;
-  }
-  if (process.env.PUPPETEER_SKIP_CHROMIUM_DOWNLOAD) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" environment variable was found.'
-    );
-    return;
-  }
-  if (
-    process.env.NPM_CONFIG_PUPPETEER_SKIP_CHROMIUM_DOWNLOAD ||
-    process.env.npm_config_puppeteer_skip_chromium_download
-  ) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" was set in npm config.'
-    );
-    return;
-  }
-  if (
-    process.env.NPM_PACKAGE_CONFIG_PUPPETEER_SKIP_CHROMIUM_DOWNLOAD ||
-    process.env.npm_package_config_puppeteer_skip_chromium_download
-  ) {
-    logPolitely(
-      '**INFO** Skipping browser download. "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" was set in project config.'
-    );
-    return;
-  }
-  downloadBrowser();
-}
-download();