eslint-plugin-react-hooks-addons
eslint-plugin-unicorn
| eslint-plugin-react-hooks-addons | eslint-plugin-unicorn | |
|---|---|---|
| 1 | 39 | |
| 9 | 3,877 | |
| - | - | |
| 0.0 | 8.6 | |
| about 1 year ago | 10 days ago | |
| JavaScript | 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.
eslint-plugin-react-hooks-addons
-
ESLint rule to check unused dependencies in React Hooks
Here is the GitHub repo: https://github.com/szhsin/eslint-plugin-react-hooks-addons
eslint-plugin-unicorn
-
Anyone using the data types Map and Set IRL?
I recently scanned out codebase with https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/prefer-set-has.md and found many instances of potential "accidentally quadratic" uses of array.includes instead. gas a nice autofix to convert to set. there are some fun and sometimes useful lint rules out there...
-
this has broken my code 3 times
There’s an ESLint rule for that (albeit in a plugin)
-
Array.reduce() feels like a cheat code/superpower if you know how to use it.
Many popular eslint configs have even introduce rules to warn on its usage for these very reasons.
-
Why are functions declared inside a component instead of directly in the file.
eslint-plugin-unicorn
- es-lint rule to force arrow functions as callbacks
- 100+ ESLint rules
-
TIL about the Nullish Coalescing Operator in Javascript (??)
I find eslint-plugin-unicorn package pretty useful for updating old code. With IE11 dead and NodeJS v12 LTS sunsetting soon, it's a brave new world.
- JS Array.foreach vs for-loops, pros and cons, which do you use and why
-
Code Review chronicles: destructuring, linting and one valid reason for Typescript
Default parameters should not be passed to a function through an object literal. The foo = {a: false} parameter works fine if only used with one option. As soon as additional options are added, you risk replacing the whole foo = {a: false, b: true} object when passing only one option: {a: true}. For this reason, object destructuring should be used instead. Linter rule
What are some alternatives?
xo - ❤️ JavaScript linter with great defaults [Moved to: https://github.com/xojs/xo]
eslint-config-xo - ESLint shareable config for XO
eslint-plugin-github - An opinionated collection of ESLint rules used by GitHub.
proposal-numeric-separator - A proposal to add numeric literal separators in JavaScript.
eslint-plugin-node - Additional ESLint's rules for Node.js
putout - 🐊 Pluggable and configurable JavaScript Linter, code transformer and formatter, drop-in ESLint superpower replacement 💪 with built-in support for js, jsx typescript, flow, markdown, yaml and json. Write declarative codemods in a simplest possible way 😏
eslint-plugin-mocha - ESLint rules for mocha
eslint-plugin-boundaries - Eslint plugin checking architecture boundaries between elements
eslint-config-canonical - The most comprehensive ES code style guide.
proposal-observable - Observables for ECMAScript
eslint-plugin-proper-ternary - ESLint rules to ensure proper usage of ternary/conditional expressions