-
Notifications
You must be signed in to change notification settings - Fork 126
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
Issues with default outputting of specific sites #115
Comments
Hi @EricFai you are right. It seems that the rule Reading the documentation (check the example) I have found this:
so it seems that Maybe @exterkamp can help and give us more information about it. @exterkamp do you know if Best regards. |
Looking at
Perhaps just add a |
Many thanks for the info @exterkamp and good idea. I'm going to do a PR with the correction, ok? Best regards. Update 👉 PR to fix the issue |
This is happening for me as well, on version 4.0.1. I just started using |
Same here @crstauf. Running both |
I was trying to use this on www.puredevelopment.com and it throws an error. I tried it on a separate site and it worked fine. I then started digging and found that if I got to /lib/output.js and comment out opportunities(lighthouseResults) [line 106] it works fine for me.
Here is the error that I got
The text was updated successfully, but these errors were encountered: