use-force-update
danger-js
Our great sponsors
| use-force-update | danger-js | |
|---|---|---|
| 3 | 6 | |
| 183 | 5,151 | |
| - | 0.4% | |
| 0.0 | 7.5 | |
| over 1 year ago | 10 days ago | |
| JavaScript | 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.
use-force-update
-
Things change with time
I get 40k downloads/week on a package that just re-renders a React function component. The entire package is five lines.
-
Empty Dependencies with useMemo or useCallback VS useRef
In this GitHub issue I essentially proposed changing:
- Can anyone answer this question?? I am stuck in it for a week :(
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?
atomic-release - Automated releases using the command pattern 📦
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code
use-prosemirror - ProseMirror + React made easy
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
cli - Get a programmable email address. Automate what happens when you receive emails. It's like Zapier for devs who hate emails.
statoscope - Statoscope is a toolkit to analyze and validate webpack bundle
use-modal-hook - 🚀 React hook for controlling modal components
prcop - A Github action for linting Pull Requests.
react-hooks-compose - Decouple Hooks from the presentational components that use them
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
chrome-extension-boilerplate-react - A Chrome Extensions boilerplate using React 18 and Webpack 5.
web-performance-research - Research in Web Performance