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.

Latest from the blog

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 when you this clash is present, is when you save your changes, the formatters will both do their job and one would add the 

. And is the formatter that would add the 

 would happen to be ESLint and not the Prettier, then you would get an ESLint error, which in some cases could even cause deployment failure within some CI/CD environments, so that clearly is an issue.

This should fix the conflicting formatter settings and resolve the issue.

Fix VS Code ESLint and Prettier conflicts.

Change VS Code default formatter

Comments