You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fresh install in project using npm install pwmetrics
Run pwmetrics https://example.com/
See error in console output
Stack trace
Launching Chrome
{ Error
at new LauncherError (/usr/local/lib/node_modules/pwmetrics/node_modules/chrome-launcher/dist/utils.js:35:22)
at new ChromeNotInstalledError (/usr/local/lib/node_modules/pwmetrics/node_modules/chrome-launcher/dist/utils.js:66:9)
at Launcher.<anonymous> (/usr/local/lib/node_modules/pwmetrics/node_modules/chrome-launcher/dist/chrome-launcher.js:145:27)
at Generator.next (<anonymous>)
at fulfilled (/usr/local/lib/node_modules/pwmetrics/node_modules/chrome-launcher/dist/chrome-launcher.js:9:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:282:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
message: 'No Chrome installations found.',
code: 'ERR_LAUNCHER_NOT_INSTALLED' }
✘ Error: Unable to complete run 1 of 1 due to connect ECONNREFUSED 127.0.0.1:9222.
Environment
pwmetrics version: ^4.2.3
Chrome version: Version 80.0.3987.116 (Official Build) (64-bit)
OS version: macOS Catalina 10.15.3
Potential Solution
Update chrome-launcher dependency to a more recent version. Lighthouse root repo uses 0.11.2 currently.
Possible solution is to set path to Chrome instance directly using flag chromePath chromePath: "/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary"
But hope there is better solution
Config / CLI options
pwmetrics https://example.com/
Steps to reproduce.
npm install pwmetrics
pwmetrics https://example.com/
Stack trace
Environment
pwmetrics
version: ^4.2.3Potential Solution
Update chrome-launcher dependency to a more recent version. Lighthouse root repo uses 0.11.2 currently.
The text was updated successfully, but these errors were encountered: