You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am investigating how to run performance audits locally with lighthouse and allow for performance budgets much like what webpack does with size budgets but giving the power to the user.
I am aware that running performance audits in a "dev environment" is less than ideal but this would be a first opt-in perf indicator and a tool to be improved upon.
The first step to doing this would be by retrieving the lighthouse results in JSON format and then evaluate them against user defined values.
Lighthouse as a standalone already enables JSON outputs but I am unable to retrieve those values from this plugin. Is it possible and an adequate functionality for this plugin?
Thanks for reading and for this OSS work :)
The text was updated successfully, but these errors were encountered:
Which would simply the code for this repository and enabled the output json flags (amongst others). If you feel so inclined I could make a PR as a proof-of-concept.
What are your thoughts on this? I realize webpack as a primarily module bundler may not make since for this kind of work.
Hello,
I am investigating how to run performance audits locally with lighthouse and allow for performance budgets much like what webpack does with size budgets but giving the power to the user.
I am aware that running performance audits in a "dev environment" is less than ideal but this would be a first opt-in perf indicator and a tool to be improved upon.
The first step to doing this would be by retrieving the lighthouse results in JSON format and then evaluate them against user defined values.
Lighthouse as a standalone already enables JSON outputs but I am unable to retrieve those values from this plugin. Is it possible and an adequate functionality for this plugin?
Thanks for reading and for this OSS work :)
The text was updated successfully, but these errors were encountered: