You're in good company

Right off the bat get your own personal site - use it as a free personal blog, or portfolio site.

Free forever

Customize your site's branding - your own custom domain, colors, layout, and more.

Tailor your branding.

Home

Visual Studio Code comes with (for better or worse) an enormous amount of features. And with that, occasionally some unexpected clashes of these features can occur and mess with our workflow.

The clash at hand for this article is the ESLint/Prettier formatter. There can be many different rules that clash between Prettier and ESLint, we will take one (arguably one of the most popular ones) - the 

What may be happening is when you save your changes, the formatters will both - format your file as well as add the 

. Meanwhile another installed formatter would remove the 

. And so when the conflicting formatter adds the 

 the other (for example ESLint) the first one (say Prettier) would show an error, which in some cases could also cause deployment failure within some CI/CD environments, so that clearly is an issue.

Change VS Code default formatter

Discussions