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

audit suggestion: track runtime errors and warnings #3109

Closed
alekseykulikov opened this issue Aug 24, 2017 · 2 comments
Closed

audit suggestion: track runtime errors and warnings #3109

alekseykulikov opened this issue Aug 24, 2017 · 2 comments

Comments

@alekseykulikov
Copy link
Contributor

Tracking this, in the way Lighthouse tracks user timing metrics may help in different cases, for example:

  • Having runtime exceptions can be a bad sign, that some javascript loaded on the pages fails, and time to load/parse is wasted.
  • warnings (console.warn) may indicate that page uses deprecated/outdated technology, that may have vulnerabilities or hurt performance.

If this is a valuable suggestion, I can try to provide a PR.
This issue may also be related to #1512

@alekseykulikov alekseykulikov changed the title audit suggestion: track runtime errors and warning audit suggestion: track runtime errors and warnings Aug 24, 2017
@patrickhulce
Copy link
Collaborator

someone else thought so too :) #2836

deprecations should already be surfaced by the "deprecations" audit that uses the console messages as the source.

@patrickhulce
Copy link
Collaborator

fixed by #2836

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

No branches or pull requests

2 participants