@xrplf/eslint-config
A super-strict TypeScript linting configuration for enforcing best practices.
Installation
First, install the needed development dependencies:
npm install --save-dev typescript @typescript-eslint/parser
npm install --save-dev eslint prettier
npm install --save-dev @typescript-eslint/eslint-plugin eslint-plugin-import eslint-plugin-prettier eslint-plugin-jsdoc eslint-plugin-tsdoc eslint-plugin-array-func eslint-plugin-eslint-comments eslint-plugin-node
npm install --save-dev @xrplf/eslint-config
Usage
Then, configure your ESLint to use the Xpring configuration. An example ESLint configuration is provided below:
module.exports = {
root: true,
parser: '@typescript-eslint/parser',
parserOptions: {
tsconfigRootDir: __dirname,
project: ['./tsconfig.json'],
sourceType: 'module',
ecmaFeatures: {
impliedStrict: true,
},
},
env: {
node: true,
es2020: true,
},
plugins: [],
extends: ['@xrplf'],
rules: {},
overrides: [],
}
Recommended Configs
We provide four different configurations.
-
The main configuration is strict and assumes that the project you're
linting uses React. This is @xrplf/eslint-config
, or @xrplf
for short.
-
If you're not using React but still want strict checking you can use
@xrplf/eslint-config/base
.
-
If you need a looser rule set for the purpose of transitioning onto the
strict rules and are using React you can use @xrplf/eslint-config/loose
.
-
Finally, if you need the looser rule set and are not using react you can
use @xrplf/eslint-config/loose-base
.
Loose Config
The looser configuration differs in the following ways:
- Longer line length limitation for functions
- More import statements allowed per file
- More parameters allowed per function
- The very strict
no-unsafe-*
rules from @typescript-eslint
are disabled - Type assertions are allowed