Create README test coverage badges from istanbul reports

Olavo Parno — Fri, 18 Sep 2020 17:51:34 +0000

There are fantastic tools for coverage badges such as Coveralls but, for free, they only cover public repositories

What then if a repository is private? Bind it to a process run locally with Istanbul Readme Badges

One can follow the very README.md of the project but in short here is what is needed:

Install it

npm i -D istanbul-badges-readme

A README.md file with additional markup into which the badges are inserted

| Statements                | Branches                | Functions                | Lines                |
| ------------------------- | ----------------------- | ------------------------ | -------------------- |
| ![Statements](#branches#) | ![Branches](#branches#) | ![Functions](#branches#) | ![Lines](#branches#) |

Run the script anywhere, either in a, e.g. pre-commit husky hook, or in a pure NPM script directly

node_modules/.bin/istanbul-badges-readme

Voilà!

Run Google's Lighthouse under authenticated websites

Olavo Parno — Thu, 17 Sep 2020 13:34:56 +0000

Have you ever run into a situation where your website demands some performance tweaks so you think of Google's Lighthouse and faces this problem:

Fear not, my friend, for there are multiple solutions for this. See the links below for more info:

In this article I am covering the Option 4 from the Auth Docs: Open a debug instance of Chrome and manually log in

Personal Notes

The application must be served either on a server or locally e.g.: http://mysite.com or http://localhost:port (seems obvious, doesn't it?)
Run chrome-debug so that the debugging browser is opened and the debugging port is shown
If the opened window closes before being able to login, use the --max-wait-for-load 15000 for 15 seconds or so (time in milliseconds)
Say the application is behind SSL certificates, auto-signed ones, and there is a need to accept the risk everytime one runs it, bypass it by using the --chrome-flags="--ignore-certificate-errors" flag
There are a bunch of other flags listed here Lighthouse CLI Flags
Final command with the beforementioned flags:

lighthouse http://localhost:3000 --disable-storage-reset --chrome-flags="--ignore-certificate-errors" --max-wait-for-load 15000 --port 45457

DEV Community: Olavo Parno

Create README test coverage badges from istanbul reports

There are fantastic tools for coverage badges such as Coveralls but, for free, they only cover public repositories

What then if a repository is private? Bind it to a process run locally with Istanbul Readme Badges

One can follow the very README.md of the project but in short here is what is needed:

Run Google's Lighthouse under authenticated websites

Have you ever run into a situation where your website demands some performance tweaks so you think of Google's Lighthouse and faces this problem:

Fear not, my friend, for there are multiple solutions for this. See the links below for more info:

In this article I am covering the Option 4 from the Auth Docs: Open a debug instance of Chrome and manually log in

Personal Notes

Thats it, a short and direct approach. There are multiple ways described in their docs but this is the most straighforward I could find.