prettier VS black

If you’ve ever set up a JavaScript or TypeScript project, chances are you've spent way too much time configuring ESLint, Prettier, and their dozens of plugins. We’ve all been there — fiddling with .eslintrc, fighting with formatting conflicts, and installing what feels like half the npm registry just to get decent code quality tooling.

Use tools like Prettier to reformat code when things get messy.

Website: prettier.io

Unfortunately, this did mean that configuration began to sprawl. At this point, I had configurations not just for Vite (shared with Vitest) and tsc, but also for Prettier, ESLint and even ShellCheck. Many of these files had shared settings that needed to match each other. This was somewhat manageable, until Vite was also in the mix.

2. Prettier Website : https://prettier.io/ Prettier is the opinionated code formatter that automatically formats your code to make it consistent and readable.it supports so many languages.

Prettier can be configured and run in multiple ways. In this example, I’ll demonstrate how to set up Prettier with a Git hook for automation in VS Code. For more examples and configurations, visit Prettier’s documentation.

Format the code: Tools like Prettier or the JavaScript beautifier can format obfuscated code.

The commonly used ones in this section are ESLint and Prettier, but there are also some confusion in their usage

VS Code is my preferred IDE and I recommend it to my team. Additionally, we use Prettier to enforce consistent, clean code style across our projects.

These requirements are not too uncommon. I have seen many projects with similar setup, with alternatives such as tox instead of nox, or black and pylint instead of ruff, etc.

Use black and isort for formatting.

black as a formatter,

repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.4.0 # Use the desired revision hooks: - id: trailing-whitespace - id: end-of-file-fixer - repo: https://github.com/psf/black rev: 23.1.0 # Use the appropriate version for your project hooks: - id: black - repo: https://github.com/pycqa/flake8 rev: 6.0.0 hooks: - id: flake8

> I appreciate that Black annoyed everyone on our team about the same amount but in different ways.

If it did affect people equally, it would be great. Unfortunately, spaces for indentation is an accessibility issue and the Black maintainers are hostile to making this configurable. Normally I am in agreement about minimising configurability, but this isn’t a matter of taste, it is making the Python ecosystem more difficult for some disabled people to participate in.

https://github.com/psf/black/issues/2798

Fortunately, Ruff makes this configurable, so you don’t have to choose between autoformatting and accessibility any more.

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.

Black (Python Code Formatter) - Black is a widely used opinionated Python code formatter that helps standardize the look of Python code. Its primary advantage is that it eliminates arguments over style, helping teams stay productive.

repos: - repo: https://github.com/psf/black rev: 22.3.0 hooks: - id: black args: [--line-length=79] - repo: https://github.com/PyCQA/isort rev: 5.10.1 hooks: - id: isort - repo: https://github.com/PyCQA/flake8 rev: 4.0.1 hooks: - id: flake8