/eslint
ESLint configurations and code-style guidelines
All packages have their respective peerDependencies and as long as you add everything required
by the package, you are good to go.
Packages itself divided by their plugin usage and made independent but at the same time integrated by keeping in mind that they can be used in conjunction with one another.
Here is just a default script section for some who tend to skip these description parts:
$ yarn add --save-dev @azimutlabs/eslint-configAll you have to do is to extend the config you want, and we'll take it from there:
{
// package.json
"eslintConfig": {
"extends": [
// Either extend ALL configurations at once...
"@azimutlabs",
// ...or piece by piece
"@azimutlabs/eslint-config-core",
"@azimutlabs/eslint-config-typescript",
"@azimutlabs/eslint-config-prettier",
]
}
}All configurations were made and tested with care. We tried to match our needs, but maybe you could find them useful as well.
 |
Collection of all @azimutlabs/eslint-config-* packages |
 |
ESLint configuration core rules |
 |
ESLint configuration for Prettier |
 |
ESLint configuration for ES6 Imports and Exports |
 |
ESLint configuration for TypeScript |
 |
ESLint configuration for React/ReactHooks |
 |
ESLint configuration for JSX Accessibility |
 |
ESLint configuration for Functional Programming |
 |
ESLint configuration for Jest testing library |
Any PR is welcomed by our @js-opensource team. Check out our contributing guidelines for more info.
