puppeteer-chromium-resolver - npm Package Compare versions

Comparing version 19.3.1 to 19.3.2

lib/install.js

@@ -0,2 +1,9 @@
+const EC = require('eight-colors');
 const PCR = require('./index.js');
-PCR();
+const { PUPPETEER_SKIP_DOWNLOAD } = process.env;
+// skip download when install
+if (PUPPETEER_SKIP_DOWNLOAD) {
+    EC.logYellow('[PCR] PUPPETEER_SKIP_DOWNLOAD');
+} else {
+    PCR();
+}

package.json

 {
     "name": "puppeteer-chromium-resolver",
-    "version": "19.3.1",
+    "version": "19.3.2",
     "description": "Tool to resolve puppeteer and chromium faster, detect local installed chromium, download chromium with custom mirror host, cache chromium revision out of node_modules, test chromium headless being launchable.",
@@ -5,0 +5,0 @@ "main": "lib/index.js",

README.md

@@ -118,9 +118,6 @@
 ### How to make puppeteer work with puppeteer-chromium-resolver
-* 1, Stop the automatic download of Chromium with following settings in .npmrc 
+* 1, Sets env PUPPETEER_SKIP_DOWNLOAD to skip download Chromium when installation (.npmrc)
 ```
-puppeteer_skip_download = true
-PUPPETEER_SKIP_CHROMIUM_DOWNLOAD = true
+PUPPETEER_SKIP_DOWNLOAD=true
 ```
-(one more setting for puppeteer v2.x)
-
 * 2, Sets env PUPPETEER_EXECUTABLE_PATH to PCR executablePath globally or pass in launch option executablePath
@@ -132,3 +129,3 @@ ```js
     const puppeteer = require("puppeteer");
-    const stats = await PCR();
+    const stats = await PCR({});
     //update global env
@@ -135,0 +132,0 @@ process.env.PUPPETEER_EXECUTABLE_PATH = stats.executablePath;

New alerts

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

28574

increased by0.5%

Lines of code

541

increased by1.31%

Worsened metrics

Number of lines in readme file

189

decreased by-1.56%

Number of low supply chain risk alerts

3

increased by50%

No dependency changes