This PR adds a new GH Actions Job to run Lighthouse checks against the build outputs.
In its current form, it runs a static server which serves the build and runs Lighthouse tests against it. This means that it doesn't resemble the production deployment exactly (which I don't have enough information about).
alternative paths
We could instead run it against inbrowser.link upon releases and update the commit status so that we can correlate lighthouse results to changes in the code.
This PR adds a new GH Actions Job to run Lighthouse checks against the build outputs.
In its current form, it runs a static server which serves the build and runs Lighthouse tests against it. This means that it doesn't resemble the production deployment exactly (which I don't have enough information about).
alternative paths