# PostCSS

# Deprecation warning

As we actively work on improving our build time and minimize the number of tools compiling/transpiling frontend code, we expect PostCSS to be one of the first tools that we will deprecate from our technology stack. Therefore, before adding PostCSS to your project, make sure that you really need it.

Here's a couple of ideas to move away from PostCSS:

• Prefer native CSS to SCSS.
• Avoid CSS nesting, it usually makes code harder to read anyway. If you really need nesting, native support is coming soon.
• Force developers to use rem by disabling the use of px with Stylelint.
• Prefix CSS properties directly in the codebase rather than relying on Autoprefixer. As browser vendors are now putting experimental features behind a flag rather than using prefixes, there aren't many CSS properties still requiring a prefix.

# Main features

The shared configuration offered by @workleap/postcss-configs includes the following features:

# Preset Env

• Stage 3
• Autoprefixer

# Getting started

To get started, follow the quick start guide to configure your first project.