<commit_before>[atom-linter]: https://atom.io/packages/linter
[atom-linter-eslint]: https://atom.io/packages/linter-eslint
[vscode-eslint]: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
[subl-packagecontrol]: https://packagecontrol.io
[subl-linter]: https://packagecontrol.io/packages/SublimeLinter
[subl-linter-eslint]: https://packagecontrol.io/packages/SublimeLinter-contrib-eslint
[subl-eslint-formatter]: https://packagecontrol.io/packages/ESLint-Formatter
[webstorm-eslint]: https://www.jetbrains.com/help/webstorm/2016.3/using-javascript-code-quality-tools.html#ESLint
[webstorm-eslint-autofix]: https://blog.jetbrains.com/webstorm/2016/09/webstorm-2016-3-eap-163-3983


# ESLint integrations with your IDE/editors

To make the whole developer experience more pleasant and convenient, it is important to configure your code editor of choice integrate with ESLint. The following can be achieved with most editors:

- Show errors/warnings inline with your code, as you type/on save
- Fix some issues immediately after saving the file so you do not have to do it manually

Letting your editor fix some issues will increase your productivity and code quality dramatically.

## Atom

Install the following packages:

- [linter][atom-linter]
- [linter-eslint][atom-linter-eslint]

For the _linter_ package, these settings are recommended:

- [x] Lint as you type
- [x] Do not lint files ignored by VCS

For the _linter-eslint_ package, these settings are recommended:

- [x] Disable when no ESLint config is found
- [x] Disable when no eslintrc file in PATH
- [x] Fix errors on save 👈

## Visual Studio Code

Install the following packages:<commit_msg>Update recommended linter config for Atom<commit_after>[atom-linter]: https://atom.io/packages/linter
[atom-linter-eslint]: https://atom.io/packages/linter-eslint
[vscode-eslint]: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
[subl-packagecontrol]: https://packagecontrol.io
[subl-linter]: https://packagecontrol.io/packages/SublimeLinter
[subl-linter-eslint]: https://packagecontrol.io/packages/SublimeLinter-contrib-eslint
[subl-eslint-formatter]: https://packagecontrol.io/packages/ESLint-Formatter
[webstorm-eslint]: https://www.jetbrains.com/help/webstorm/2016.3/using-javascript-code-quality-tools.html#ESLint
[webstorm-eslint-autofix]: https://blog.jetbrains.com/webstorm/2016/09/webstorm-2016-3-eap-163-3983


# ESLint integrations with your IDE/editors

To make the whole developer experience more pleasant and convenient, it is important to configure your code editor of choice integrate with ESLint. The following can be achieved with most editors:

- Show errors/warnings inline with your code, as you type/on save
- Fix some issues immediately after saving the file so you do not have to do it manually

Letting your editor fix some issues will increase your productivity and code quality dramatically.

## Atom

Install the following packages:

- [linter][atom-linter]
- [linter-eslint][atom-linter-eslint]

For the _linter_ package, these settings are recommended:

- [x] Lint as you type
- [x] Do not lint files ignored by VCS

For the _linter-eslint_ package, these settings are recommended:

- [x] Disable when no eslintrc file in PATH
- [x] Fix errors on save
- [x] Ignore fixable rules while typing

## Visual Studio Code

Install the following packages:
{'fraction_non_alphanumeric': 0.1019202363367799, 'fraction_numerical': 0.013589364844903988, 'mean_word_length': 4.95079086115993, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 18, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6517222', 'n_tokens_mistral': 1086, 'n_tokens_neox': 1035, 'n_words': 321}