That’s a tool we made, but it uses lighthouse under the hood. We’ve added our own custom audits and gatherers though. If you want to read up on how to do that, here‘s an example: https://github.com/GoogleChrome/lighthouse/tree/master/docs/recipes/custom-audit.
Hi Ola! Thanks for your feedback. Can you clarify what is wrong with this statement:
> any render is delayed until your stylesheets have been fully loaded.
FWIW, this statement was not about <link> elements with a media attribute.
What Harry Roberts proposes will likely not work for us due to the way we write our CSS.
I saw your PR. I also saw the amount of code you had to write to make it work, and figured there could be a more simple solution.
Additionally, the chance that the behavior of code-splitting will change in our application is small. It’s probably in the same ball park as minifying your code, or extracting static CSS. Things I…
You’d require the file, and include it in webpack.config.js, via the `plugins` key. You probably only want to run it when using webpack in watch mode (`webpack -w`). Here’s my webpack.config.js, look for ProtractorTestRunnerPlugin, and here’s the script we use to start webpack in watch mode (`e2e-dev`).
There’s a bunch of links to the source code in the other article (https://medium.com/@plestik/the-offline-experience-or-saying-goodbye-to-imperative-data-fetching-9b2fa487eea7#6eec). The library isn’t ready for use outside of our application. That might change in the future but I’d have to find some time, and I need to make sure it works for Angular 2.
Agreed, but that unfortunately doesn’t make sense in this situation as far as I can tell. I need it to work in all browsers, and I need to be able to differentiate between cached requests and actual requests (if that makes sense). We do use sw-precache for assets, though, lovely tool.