-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Protocol error (Target.getTargetInfo): Protocol error (Target.getTargetInfo): 'Target.getTargetInfo' wasn't found #209
Comments
Can you try with Node and not bun and see if there's still an issue? |
I tested with
I then runned again with debug mode
Log seem the same
Tested changing the website tested
It worked, definitely a bug on https://github.com/GoogleChrome/lighthouse or a problem on the website itself as it doesn't work on page speed insight either https://pagespeed.web.dev/analysis/https-antares-majestico-it/csio0s1h42?form_factor=mobile weird, I wonder what's the problem with the website. |
Will move the issue to lighthouse |
Hmm I've updated Lighthouse to v12 in v0.12.0 but maybe it's not solved entirely yet. |
Hi, bug is still open on lighthouse GoogleChrome/lighthouse#15739 so probably not |
Describe the bug
Not sure if this is a bug (here).
On Github actions I get the error
Protocol error (Target.getTargetInfo): Protocol error (Target.getTargetInfo): 'Target.getTargetInfo' wasn't found
Seem like that it detect the routes correctly, but at the time it have to test the 2 routes it breaks, I saw GoogleChrome/lighthouse#15586 but the version used should be the latest stable
[info] [Unlighthouse] Using system chrome located at: /usr/bin/google-chrome-stable.
Result looks like this https://antares-performance.netlify.app/
If I bug this is probably more a lighthouse problem (https://github.com/GoogleChrome/lighthouse) but just want to know if anyone else experiencing the same problem.
My workflow
Also tried:
Full build log:
Not sure If I m missing something,
thanks.
Reproduction
No response
System / Nuxt Info
The text was updated successfully, but these errors were encountered: