eslint-plugin-unicorn VS eslint-config-xo

XO. This feels like the Black of Typescript linting. XO has styles for everything and is very opinionated. This can be nice, because it takes a lot of code style decisions off of your plate. But beware it can be cumbersome to implement in the middle of a project because it will require extensive reformatting. In lieu of XO, I found Unicorn opinionated enough and more immediately useful.

Recently, we chose to add the Unicorn plugin, which contain dozens of ESlint rules. It can feel overwhelming at first because it triggers hundreds of errors. Fortunately, we discovered eslint-nibble: a command line tool that helps adding rules one by one with a graphical interface.

I recently scanned out codebase with https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/prefer-set-has.md and found many instances of potential "accidentally quadratic" uses of array.includes instead. gas a nice autofix to convert to set. there are some fun and sometimes useful lint rules out there...

There’s an ESLint rule for that (albeit in a plugin)

Many popular eslint configs have even introduce rules to warn on its usage for these very reasons.

eslint-plugin-unicorn

I find eslint-plugin-unicorn package pretty useful for updating old code. With IE11 dead and NodeJS v12 LTS sunsetting soon, it's a brave new world.

XO. This feels like the Black of Typescript linting. XO has styles for everything and is very opinionated. This can be nice, because it takes a lot of code style decisions off of your plate. But beware it can be cumbersome to implement in the middle of a project because it will require extensive reformatting. In lieu of XO, I found Unicorn opinionated enough and more immediately useful.

Based on your requirements and environment, answer the questions accordingly. At least with eslint version 8.0.1, you are only presented with 2 style guides: standard and XO. Personally, I prefer the standard styling guide but at any give time, it is a personal choice and as such feel free to choose any from a bunch of available options. Once all dependencies are installed, ensure that you have the following packages added as devDependencies to your project:

# 1 - Inicio da configuração do eslint yarn eslint --init # 2 - Escolha a opção "To check syntax, find problems, and enforce code style" How would you like to use ESLint? To check syntax only To check syntax and find problems ❯ To check syntax, find problems, and enforce code style # 3 - Escolha a opção "JavaScript modules (import/export)" What type of modules does your project use? ❯ JavaScript modules (import/export) CommonJS (require/exports) None of these # 4 - Escolha a opção "React" Which framework does your project use? ❯ React Vue.js None of these # 5 - Escolha a opção "Yes" Does your project use TypeScript? No ❯ Yes # 6 - Pressionando a barra de espaço, deixe selecionado somente a opção "Browser" Where does your code run? ✔ Browser Node # 7 - Escolha a opção "Use a popular style guide" How would you like to define a style for your project? … ❯ Use a popular style guide Answer questions about your style Inspect your JavaScript file(s) # 8 - Escolha a opção "Use a popular style guide" How would you like to define a style for your project? … ❯ Use a popular style guide Answer questions about your style Inspect your JavaScript file(s) # 9 - Escolha a opção "Airbnb" Which style guide do you want to follow? ❯ Airbnb: https://github.com/airbnb/javascript Standard: https://github.com/standard/standard Google: https://github.com/google/eslint-config-google XO: https://github.com/xojs/eslint-config-xo # 10 - Escolha a opção "JavaScript" What format do you want your config file to be in? … ❯ JavaScript YAML JSON # 11 - Escolha a opção "Yes" Would you like to install them now with npm? No ❯ Yes

XO - Enforce strict code style using the JavaScript happiness style.