eslint-config-vtex
v15.1.0
Published
VTEX's eslint config
Downloads
50,851
Maintainers
Readme
eslint-config-vtex
This package provides VTEX's .eslintrc
as an extensible shared config.
Installation
Give that you already have ESLint installed, run:
yarn add -D eslint-config-vtex typescript prettier
Usage
After installing the module, just add it to your extends
array inside your .eslintrc
.
// .eslintrc
{
"extends": ["vtex"]
}
As any other eslint preset, it's possible to override some rules and configurations. We encourage trying to keep the closest possible to the preset rules, but every project is different and sometimes overriding is needed, use it carefully.
For typescript
The preset will automatically load Typescript rules when dealing with .ts
or .tsx
files. However, there are some rules that require type-checking. This means that a tsconfig.json
, which includes all files supposed to be linted, must be present. If your existing configuration does not include all of the files you would like to lint, you can create a separate tsconfig.eslint.json
, at the root of your project, as follows:
// tsconfig.eslint.json
{
"extends": "./tsconfig.json",
"include": ["**/*.ts", "**/*.tsx", "**/*.js"],
"exclude": []
}
And you should be good to go.
For Javascript
Sometimes you want to use modern, not yet officially supported, syntax in your Javascript files, such as dynamic import()
. This can be achieved by using the babel-eslint
parser. For size reasons, we don't include it in this preset but it's extremely simple to configure it:
yarn add -D babel-eslint
// .eslintrc
{
"extends": "vtex",
"parser": "babel-eslint",
"parserOptions": {
"sourceType": "module"
}
}
If a project uses both Typescript and Javascript, you can configure the parser inside an override
block:
// .eslintrc
{
"extends": "vtex",
"overrides": [
{
"files": ["*.js", "*.jsx"],
"parser": "babel-eslint",
"parserOptions": {
"sourceType": "module"
}
}
]
}
Please check the babel-eslint
documentation for further options.