Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/okp4/eslint-config-okp4
📜 ESLint shareable config used @okp4
https://github.com/okp4/eslint-config-okp4
craft eslint eslint-config eslint-typescript prettier typescript
Last synced: 3 days ago
JSON representation
📜 ESLint shareable config used @okp4
- Host: GitHub
- URL: https://github.com/okp4/eslint-config-okp4
- Owner: okp4
- License: bsd-3-clause
- Created: 2022-03-09T10:34:50.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-08-30T23:36:47.000Z (2 months ago)
- Last Synced: 2024-09-27T12:07:28.235Z (about 1 month ago)
- Topics: craft, eslint, eslint-config, eslint-typescript, prettier, typescript
- Language: JavaScript
- Homepage:
- Size: 282 KB
- Stars: 5
- Watchers: 2
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-ccamel - okp4/eslint-config-okp4 - 📜 ESLint shareable config used @okp4 (JavaScript)
README
# eslint-config
> ESLint [shareable config](https://eslint.org/docs/developer-guide/shareable-configs.html) used @[OKP4](https://github.com/okp4)
[](https://github.com/okp4/eslint-config-okp4/actions/workflows/lint.yml)
[](https://github.com/okp4/eslint-config-okp4/actions/workflows/build.yml)
[](https://conventionalcommits.org)
[](https://github.com/okp4/.github/blob/main/CODE_OF_CONDUCT.md)
[](https://opensource.org/licenses/BSD-3-Clause)
## Purpose & Philosophy
This repository holds the shared [ESLint](https://eslint.org) configuration used for all our [TypeScript](https://www.typescriptlang.org) projects at [OKP4](https://github.com/okp4).
The current configuration enforces strict dogmatic rules - (too strict you might think)- in addition to those recommended by the various linting extensions available such as ESLint itself, and various plugins such as `react`, `react-hooks`, `typescript-eslint`...
Indeed, at [OKP4](https://github.com/okp4) we are convinced that the quality of the code depends on clear and consistent coding conventions, with an automated enforcement.
The rules configured are mainly based on two pillars:
- [React](https://reactjs.org): We encourage as much as possible an architectural approach focusing on Functional Components. That's why we enforce a strict mode and a High Severity according to the recommendations of Facebook Core ([React Team](https://reactjs.org/community/team.html)).
- [TypeScript](https://www.typescriptlang.org): At [OKP4](https://github.com/okp4), we love Type Safety, and we are deeply conviced that better type safety means less error in production. That's one of the reasons we chose `TypeScript` over `JavaScript`. We've therefore adopted very strict Type Checking rules in order to take advantage of the best of `TypeScript`.
## Installation
### NPM
`npm` version must be at least equal to 7.0.0 to install automatically peer-dependencies (see )
```sh
npm i @okp4/eslint-config
```
### Yarn
If you want to use `yarn`, you must first list all peer dependencies using `npm` and add then individually with `yarn`.
First, list the peer dependencies and versions:
```sh
npm info @okp4/eslint-config@latest peerDependencies
```
Then run the following command line for each listed peer dependency.
```sh
yarn add --dev @
```
## Usage
### ESLint
Create your `.eslintrc` configuration file, taking care to properly inform the source of the project used for the TypeScript parser:
```json5
{
"extends": "@okp4", // may be combined with other shareable configurations
"parserOptions": {
"project": "./tsconfig.json"
}
}
```
### Prettier
Cretate your `.prettierrc.js` configuration file :
```javascript
module.exports = {
...require('@okp4/eslint-config/.prettierrc.js')
}
```
## Contributing
So you want to contribute? Great. We appreciate any help you're willing to give. Don't hesitate to open issues and/or submit pull requests.
Remember that this is the configuration we use at [OKP4](https://github.com/okp4), and that we apply everywhere in our private and public projects. This is why we may have to refuse change requests simply because they do not comply with our internal requirements, and not because they are not relevant.