prettier VS Standard

Another trendy tool is Prettier. It makes your code look beautiful to developers' eyes (yours included).

https://typicode.github.io/husky/#/ https://docs.microsoft.com/sk-sk/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.1 https://prettier.io/ https://eslint.org/

We’ve made much of if automatic. Our editors are configured to take care of styles and formatting; TypeScript provides a first layer of testing; and shared git hooks run project-specific static checks.

Prettier

Format, e.g., with Prettier on save.

A linter is a tool that analyzes your code for how it is styled (where do curly braces go etc) but can also do things like checking if variables are correctly named or not mutated. In the webdev world 2 popular linting tools are https://prettier.io and https://eslint.org :)

Automated quality assurance on the fundamental level. Tools such as eslint & prettier on the frontend; Flake8 & black in python help you ensure code-style consistency & protects from the simplest errors you could introduce to your codebase. Setting them up & applying all initial changes takes time, but the most difficult is to get all team members on board & get them to use those tools consistently - especially before merging the changes to the main branch.

Prettier is a great tool for maintaining consistent formatting in a project. Prettier works quite well for a monorepo. One can simply define a .prettierrc file in the root of the monorepo and run Prettier using that configuration file. It will automatically apply to all packages in the monorepo.

As stated in the official Official Prettier Website it doesn't support C files, mostly just frontend web development related filetypes like HTML, CSS, JS, YAML, etc. For C and C++ you have to use abother formatter. My favorite is clang-format. It should be installed by default in VSCode when you installed the C/C++ extension from Microsoft. Just run the command "Format Document" from the command palette (don't remember if that's the exact command name". You can configure the formatting styles in your settings.json following the configuration options stated in the official clang-format guide.

- https://standardjs.com/

JavaScript Standard style guide on GitHub

# 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

Standard JS.

The JS Open Source Community is filled with people grifting things like this. Quite notably, there's a linter called JS Standard Style, which actually has nothing to do with JS Standards.

It's marketed as if it was a standard, the fact that it isn't is tucked away in the readme, and also -- the entire project is just a wrapper around someones .eslintrc file, yet barely any credit is given to the ESLint devs who do all the work.

Go ahead and read the readme here, https://github.com/standard/standard. Could you genuinely tell this wasn't really a JS Standard at a glance? Could you tell this was just a config file for someone elses work? None of the donations go upstream to eslint by the way.

Hell, the actual config file is hidden inside a sub repo:

https://github.com/standard/eslint-config-standard

which has the audacity to claim

> This module is for advanced users. You probably want to use standard instead :)

It's a config file for someone elses program! Why does this library go through so much effort to hide that it's just someones config file? Why on earth is it called JS Standard Style?

The whole community is filled with slimy nonsense like this.