danger-js
web-performance-research
Our great sponsors
| danger-js | web-performance-research | |
|---|---|---|
| 6 | 2 | |
| 5,148 | 708 | |
| 0.4% | 1.0% | |
| 7.5 | 9.3 | |
| about 1 month ago | 5 days ago | |
| TypeScript | JavaScript | |
| 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.
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).
web-performance-research
-
Profiling & Optimizing a React Application with DevTools
There are many resources about web performance out there. If you are interested in this topic, you should definitely follow the Web Performance Research repository.
-
React PWA Performance Study Case
I have some resources I used along the way while doing this project. I hope it can be helpful to you too: Web Performance Studies.
What are some alternatives?
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
gotty - Share your terminal as a web application
statoscope - Statoscope is a toolkit to analyze and validate webpack bundle
prcop - A Github action for linting Pull Requests.
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
use-force-update - React Hook to force your function component to update
action - Github Actions for running CodSpeed in your CI
architecture_decision_record - Architecture decision record (ADR) examples for software planning, IT leadership, and template documentation
codeball-action - 🔮 Codeball – AI Code Review that finds bugs and fast-tracks your code
gradle-build-action - Execute your Gradle build and trigger dependency submission