prettier VS ESLint

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.

There are many tools that help developers eliminate possible errors and bugs, and in the end, ship more robust and maintainable code. Among them, the most commonly used static code analysis tool is ESLint.

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/

Eslint

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.

ESLint provides sophisticated analysis of JavaScript or TypeScript sourcecode. Thankfully it can be configured as easy as Prettier for a monorepo. We can define an .eslintrc.json file in the project root and that will apply to all files in the Monorepo.

Use eslint, but that's not an alternative, you should lint your code anyway and benefit from (mostly) helpful hints and warnings.

This worked very well so I decided to also add actions to run Prettier and ESLint automatically. I looked through how Telescope implements Continuous Integration and I created a similar setup for dodo-SSG.