statoscope
danger-js
Our great sponsors
statoscope | danger-js | |
---|---|---|
4 | 6 | |
1,375 | 5,151 | |
2.0% | 0.4% | |
7.8 | 7.5 | |
4 months ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
statoscope
-
What is a package you need, but it does not exist
There’s a demo available here: https://statoscope.tech/ We use it at my work
-
Brand new toolkit to analyze and validate your webpack bundle
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.
-
Statoscope - brand new toolkit to analyze and validate your bundle
In this post I would like to share Statoscope with you.
danger-js
-
Enforcing ESLint rules: A guide to taming codebase chaos
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.
-
How We Started Managing BSA Delivery Processes on GitHub
commitlint & dangerjs. Linters that help maintain consistency in all user-provided information related to Git and GitHub (commits, branch names, PR titles, etc.).
- DangerJS – automate common code review chores
- PRcop – open-source Pull Request linter for Github Actions built with JS
-
How to deal with teammates forcing personal preference into code reviews and nit picking everything?
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.
-
React PWA Performance Study Case
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).
What are some alternatives?
ngd - View the dependencies tree of you Angular application
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code
packageanalyzer - A framework to introspect Node.js packages
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
dart-code-metrics - Software analytics tool that helps developers analyse and improve software quality.
prcop - A Github action for linting Pull Requests.
zx - A tool for writing better scripts
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
cli - Kontent.ai command line interface supporting migrations scripts processing written by Management SDK JS.
use-force-update - React Hook to force your function component to update
codeql-action - Actions for running CodeQL analysis
web-performance-research - Research in Web Performance