Automatic CDN-enabled deployments with SSL to the cloud. No hassle, no dev-ops!

Auto-deployments

Add custom domain and personalize your site to grow your own brand. We'll do the rest.

Grow your brand

Opt-in to premium publishing and earn by writing and teaching. Engagement-based rewards, coming soon.

Side income

Easy to use, Medium-like article publishing with drafts and granular visibility and SEO controls.

Publish in minutes

Fully-featured course management, including tier-based payments are coming soon.

Manage courses

No matter the type of content you work on we will do the heavy lifting for you! Then tweak as needed.

Baked-in, tasty SEO

Digital nomad essentials

Meet & Greet

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

Change VS Code default formatter

Comments