Add toplevelwarning about old Chrome
See original GitHub issueProvide the steps to reproduce
- Run LH on
https://d13z.dev
usinglighthouse@next
npm package - Performance score in result is
null
What is the current behavior?
After running lighthouse from a nodejs script, the performance score result is null
.
Other categories have their score calculated properly.
What is the expected behavior?
If the score can not be calculated, it should throw an error or warning. Otherwise, it should calculate and save the performance score properly.
Result of the report: https://api.jsonbin.io/b/5e7a162079d7e24dd30e365d report: https://googlechrome.github.io/lighthouse/viewer/?gist=d3b79a47e01590171bd7536f2980c145
package.json
{
"version": "1.1.1",
"main": "build/server.js",
"private": true,
"license": "MIT",
"scripts": {
},
"engines": {
"node": "^12.9.1"
},
"lint-staged": {
"*.{js,jsx,ts,tsx}": "eslint"
},
"husky": {
"hooks": {
"pre-commit": "pretty-quick --staged && lint-staged"
}
},
"devDependencies": {
"@typescript-eslint/eslint-plugin": "^2.15.0",
"@typescript-eslint/parser": "^2.15.0",
"cross-env": "^5.2.1",
"devtools-protocol": "0.0.692805",
"eslint": "^6.8.0",
"eslint-config-prettier": "^6.9.0",
"eslint-config-standard": "^14.1.0",
"eslint-plugin-import": "^2.19.1",
"eslint-plugin-node": "^10.0.0",
"eslint-plugin-prettier": "^3.1.2",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-standard": "^4.0.1",
"husky": "^3.1.0",
"lint-staged": "^9.5.0",
"prettier": "^1.19.1",
"pretty-quick": "^1.11.1",
"ts-node": "^8.5.4",
"typescript": "^3.7.4"
},
"dependencies": {
"@types/bluebird": "^3.5.29",
"@types/puppeteer": "^1.20.3",
"@types/request": "^2.48.4",
"@types/request-promise": "^4.1.45",
"aws-sdk": "^2.600.0",
"bluebird": "^3.7.2",
"express": "^4.17.1",
"fs-extra": "^8.1.0",
"interval-promise": "^1.3.0",
"lighthouse": "^6.0.0-beta.0",
"puppeteer": "^1.20.0",
"request": "latest",
"request-promise": "^4.2.5"
}
}
Environment Information
- Affected Channels:
- Lighthouse version: 6.0.0-beta.0
- Chrome version: 80.0.3987.149
- Node.js version: 12.13.0 / 13.8.0
- Operating System: MacOS 10.15.3 / Windows 10 2004 (compilation build 19041.153)
Related issues
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Manage warnings about unsafe sites - Computer
You'll see a warning if the content you're trying to see is dangerous or deceptive. These sites are often called "phishing" or "malware"...
Read more >Avoiding the not secure warning in chrome
A warning has been added to the URL bar. ... This means that the top-level page must be HTTPS and, if the input...
Read more >28 New Chrome Exploits Found, Google Release Urgent ...
Google classifies nine of these new hacks as carrying a 'High' threat level and warns users that all 28 vulnerabilities affect Chrome across ......
Read more >How to Fix ERR_SSL_OBSOLETE_VERSION Warning ...
The Dangers of Using Older TLS Versions on Your Website. So what does this mean for the future of Chrome browsers, and more...
Read more >How to fix Google chrome SSL certificate errors in a few ...
That said, sometimes there can be an issue on the user's end to trigger this warning. Luckily, fixing these problems isn't too complicated....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think a null value will always be due to older versions of Chrome (needs citation). We could emit a warning specifying that.
Ah if you were using an older version of Chromium that ships with puppeteer then that would absolutely explain it 😃