Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lighthouse 2.80 #471

Closed
mcaple opened this issue Jan 24, 2018 · 2 comments
Closed

Lighthouse 2.80 #471

mcaple opened this issue Jan 24, 2018 · 2 comments

Comments

@mcaple
Copy link

mcaple commented Jan 24, 2018

Do you want to request a feature or report a bug?

What is the current behaviour?

If the current behaviour is a bug, please provide the steps to reproduce.

What is the expected behaviour?

If this is a feature request, what is motivation or use case for changing the behaviour?

Please mention other relevant information.

  • Node version
  • npm version
  • Operating system
  • CLI version
  • Browser

Hi,
You state that lighthouse returns 100% compatible. Just wanted to let you know that that does not appear to be the case with Lighthouse 2.80. Is it your intention to keep this percentage.

Thanks
Mark

@lukeed
Copy link
Member

lukeed commented Jan 24, 2018

Thanks! We'll look into it since it's been a while. Lighthouse criteria changes every so often.

@reznord
Copy link
Member

reznord commented Mar 28, 2018

Hi @mcaple I ran a lighthouse test on https://clidemo.preactjs.com/ and I get a 💯PWA score.

screen shot 2018-03-28 at 9 26 35 am

Note: Run the lighthouse audit in incognito window for apt results, or else your extensions might effect the lighthouse scores

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants