In this course, you'll learn how to setup Prettier and Stylelint from the ground up. Whether you're working in a team or alone, you'll save a bunch of time on hunting bugs and dealing with annoying code inconsistencies that pile up with time and can quickly get out of hand.
You'll see even greater benefits if you're working in a team. You'll gain an understanding of how to get your entire team and even organization to adhere to the same, consistent, sensible standard, and you will never again have to worry that somebody will commit code that isn't up to your fundamental standards.
Prettier and Styelelint are fantastic tools, often underused because of their complexity.
- It's difficult and challenging to set them up properly.
- It's hard to quantify their value in a team and even more for projects where you're the only one working on CSS.
- Stylelint alone has 170+ built-in rules, and it’s impossible to figure out where to start or what to configure.
- Just configuring Prettier & Stylelint properly isn't enough; you need to know how to fully integrate them into your workflow.
- Getting your entire team and organization on board can be challenging.
I address all those pain points in Mastering Prettier & Stylelint—when you finish it, you'll understand exactly how to approach challenges you might face, how to set up the tools, how to integrate them into your workflow, and how to introduce them to your team and even across different teams or products in your company.
By the end of the course...
- You'll have a clear idea of how to setup Prettier and Stylelint from the ground up.
- You’ll understand how to configure both Prettier & Stylelint to work for you without having to dig into every configuration option available.
- You’ll have a profound understanding of how to integrate Prettier & Stylelint into your workflow—from Code Editor to commit hooks, testing tools, and even continuous integration.
- You'll know how to effortlessly keep your entire team and even organization adhering to consistent, sensible coding standards, from common stylistic conventions to specific guidelines around Stylesheet rules.
- You will no longer have to deal with trivial, time-consuming mistakes that can be automatically detected and even fixed.
- You'll save a ton of time by being able to confidently forget about code formatting, property reordering, and reviewing pull requests for basic mistakes like improper whitespace, duplicated rules, or overly specific selectors.