danger-js VS statoscope

Make sure to not accept any Pull Request with commented ESLint errors to ensure a continuous improvement of your codebase quality. Some tools can help you to automate this part of the review, such as Danger JS.

commitlint & dangerjs. Linters that help maintain consistency in all user-provided information related to Git and GitHub (commits, branch names, PR titles, etc.).

Does your team use any automatic code formatting or linting tools? E.g. for TypeScript or JavaScript, a combination of Prettier and ESLint, with a well understood and agreed-upon configuration, can avoid this kind of back and forth. Danger.js is a good way to handle the higher level concerns that cannot be addressed at the syntax level.

This tool is run in our CI pipeline for every PR and the result is shown in the Github PR (it uses Danger behind it).

There’s a demo available here: https://statoscope.tech/ We use it at my work

Statoscope is a modern tooklit for analyzing and validating your bundle. You can try Statoscope by simply dropping the stats of your build into https://statoscope.tech or using a webpack plugin that will generate a UI-based report about your build. This report will show you full information about your build, NPM packages duplicates, and even the download speed of your bundle to a client browser. With this UI report, you can make your own requests to stats and generate your own reports about your bundle. This is very similar to python notebook, but for webpack stats and is possible thanks to a special query language.

In this post I would like to share Statoscope with you.