eslint-plugin-canonical
eslint-config-canonical
eslint-plugin-canonical | eslint-config-canonical | |
---|---|---|
4 | 8 | |
138 | 612 | |
6.5% | 1.3% | |
8.0 | 9.0 | |
about 1 month ago | 4 days ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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-canonical
-
is there a utility for auto adding .ts or .tsx extension to imports?
Here is the implementation for others searching for it https://github.com/gajus/eslint-plugin-canonical/blob/main/src/rules/requireExtension.ts Most of the complexity is hidden by eslint-module-utils/resolve, luckily.
-
[AskJS] What ESLint rules do you use to achieve better isolation of components?
You can track progress here https://github.com/gajus/eslint-plugin-canonical/pull/16
- eslint-config-canonical: 1,000+ rules ESLint rules
eslint-config-canonical
-
ESLint adoption guide: Overview, examples, and alternatives
Over the years, many popular and widespread shared configurations have been developed. However, with every breaking change in ESLint, the community projects need to migrate. Therefore, it's important to check the compatibility with ESLint v9 support and flat config support in particular before using a third-party npm package: To use a shared ruleset, you can also leverage the CLI option --config. The following installs a third-party configuration, eslint-config-canonical:
-
ESLint-config-canonical: 1k rules ESLint rules
https://github.com/gajus/eslint-config-canonical
I will repost this every couple of years, as it now has been 8 years since I regularly update this config. For most projects, adopting this is going to be as simple as:
{
- Show HN: Canonical – 1k ESLint rules to automate code conventions
-
semver: v1 vs v1000
It's something that keeps coming up in GitHub issues on my various projects... they point at my project version, which could be v7, v28, v33, and then say "This project versioning is bad." or "This project API is unstable.", etc. and then compare them to projects that are v1, as if that somehow proves their point.
-
Why is is prettier used if eslint can format?
For anyone would would like to migrate from Prettier to ESLint, https://github.com/gajus/eslint-config-canonical covers everything that Prettier does and a lot (a lot) more.
-
ESLint plugin for Storybook
Should we add it to https://github.com/gajus/eslint-config-canonical ?
- eslint-config-canonical: 1,000+ rules ESLint rules
What are some alternatives?
eslint-plugin-unicorn - More than 100 powerful ESLint rules
quick-lint-js - quick-lint-js finds bugs in JavaScript programs
dependency-cruiser - Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
eslint-config-prettier - Turns off all rules that are unnecessary or might conflict with Prettier.
roarr - JSON logger for Node.js and browser.
eslint-plugin-storybook - 🎗Official ESLint plugin for Storybook
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
rustfmt - Format Rust code