https://github.com/jitesoft/eslint-config
ESLint Configuration used by the Jitesoft organization.
https://github.com/jitesoft/eslint-config
eslint hacktoberfest jitesoft preset
Last synced: about 2 months ago
JSON representation
ESLint Configuration used by the Jitesoft organization.
- Host: GitHub
- URL: https://github.com/jitesoft/eslint-config
- Owner: jitesoft
- License: mit
- Created: 2019-04-18T08:39:44.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2024-11-16T07:08:30.000Z (over 1 year ago)
- Last Synced: 2025-06-21T11:03:27.889Z (12 months ago)
- Topics: eslint, hacktoberfest, jitesoft, preset
- Language: JavaScript
- Homepage:
- Size: 961 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# @jitesoft/eslint-config
[](https://www.npmjs.com/package/@jitesoft/eslint-config)
[](https://dev.snyk.io/test/npm/@jitesoft/eslint-config)
[](https://www.npmjs.com/package/@jitesoft/eslint-config)
[](https://opencollective.com/jitesoft-open-source)
Semi-standard shareable config to make it easier to modify by Jitesoft organization.
Installation:
```bash
npm i --save-dev @jitesoft/eslint-config
yarn add --dev @jitesoft/eslint-config
```
## Configurations
There are four configurations available:
`default`, `node`, `browser`, `jsx` and `jest`.
As expected, the Node and Browser configurations are set to use globals for the environment.
The `default` configuration is a mixed node/web configuration, while the `jest` configuration
is created for code which uses the `jest` test framework.
## Usage
To extend the base/default config, just use the scoped name as such:
```json
{
"extends": "@jitesoft"
}
```
To be able to use the other configurations, the whole name have to be included:
```json
{
"extends": "@jitesoft/eslint-config/jest"
}
```
## QA
Q:
Why?
A:
For an organization it's easier to keep a bundle of configurations than using a million little packages in each package.json file.
This package contains all the standards used by Jitesoft.
Further more, if we wish to change any rules, it's a lot easier to do that in our own package than propagate it through settings files in all
repositories!
Q:
Why hard versions in the package.json file?
A:
To make sure that all the packages are in the exact version that we thought they where at each publish, the versions
of the sub-packages have been set to exact versions. It's hard to test and make sure that everything works as intended in case
some users use later or earlier versions (even if it is patch versions!) without knowing.
Q:
Why semistandard and not just standard?!
A:
Cause semicolon is best. Thats why!
Q:
Why spaces instead of tabs?!
A:
....