StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
PostCSS
ByPostCSSPostCSS

PostCSS

#8in Templating Languages & Extensions
Discussions8
Followers546
OverviewDiscussions8

What is PostCSS?

PostCSS is a tool for transforming CSS with JS plugins. These plugins can support variables and mixins, transpile future CSS syntax, inline images, and more.

PostCSS is a tool in the Templating Languages & Extensions category of a tech stack.

PostCSS Pros & Cons

Pros of PostCSS

  • ✓The "babel" of CSS
  • ✓Customizable
  • ✓Autoprefixer
  • ✓Variables
  • ✓CSS MQPacker
  • ✓Mixins
  • ✓PostCSS Flexbugs Fixes

Cons of PostCSS

No cons listed yet.

PostCSS Alternatives & Comparisons

What are some alternatives to PostCSS?

Sass

Sass

Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.

Animate.css

Animate.css

It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness.

Less

Less

Less is a CSS pre-processor, meaning that it extends the CSS language, adding features that allow variables, mixins, functions and many other techniques that allow you to make CSS that is more maintainable, themable and extendable.

Autoprefixer

Autoprefixer

It is a CSS post processor. It combs through compiled CSS files to add or remove vendor prefixes like -webkit and -moz after checking the code.

css-loader

css-loader

The css-loader interprets @import and url() like import/require() and will resolve them.

Stylus

Stylus

Stylus is a revolutionary new language, providing an efficient, dynamic, and expressive way to generate CSS. Supporting both an indented syntax and regular CSS style.

PostCSS Integrations

Jetpack, React.js Boilerplate, tachyons, JSFiddle, Basscss and 7 more are some of the popular tools that integrate with PostCSS. Here's a list of all 12 tools that integrate with PostCSS.

Jetpack
Jetpack
React.js Boilerplate
React.js Boilerplate
tachyons
tachyons
JSFiddle
JSFiddle
Basscss
Basscss
Lad
Lad
Adobe Dreamweaver
Adobe Dreamweaver
Devsync
Devsync
Primo
Primo
Stitches
Stitches
Tailwindcss JIT
Tailwindcss JIT
astroturf
astroturf

PostCSS Discussions

Discover why developers choose PostCSS. Read real-world technical decisions and stack choices from the StackShare community.

Zarema Khalilova
Zarema Khalilova

Frontend Team Lead at Uploadcare

Dec 4, 2018

Needs adviceonSassSassLessLessPostCSSPostCSS

We in our #Frontend team prefer to use the modern and clean syntax of #CSS instead of Sass or Less. On bundle step, we use post-processing by PostCSS to add prefixes, minify code, uploading assets and more. PostCSS get CSS more powerful, it‘s a fantastic tool.

0 views0
Comments
Lee Benson
Lee Benson

Nov 30, 2018

Needs adviceonReactReactGraphQLGraphQLApolloApollo

ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #@{css}|topic:477| #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

0 views0
Comments
Dmitry Mukhin
Dmitry Mukhin

Engineer at Uploadcare

Sep 13, 2018

Needs adviceonDjangoDjangoPythonPythonReactReact

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

0 views0
Comments
Thibault Maekelbergh
Thibault Maekelbergh

Web Tech Lead

Aug 9, 2016

Needs adviceonPostCSSPostCSS

We wrote a lot of flexbox and css that needed prefixing. PostCSS + Webpack was the best option here. PostCSS

0 views0
Comments
Tim Lucas
Tim Lucas

Co-Founder, Designer

Apr 5, 2016

Needs adviceonPostCSSPostCSS

PostCSS handles compiling node-based CSS libraries, including BassCSS (the whole site is only ~85 lines of custom CSS). It also does auto-vendor-prefixing and support for CSS variables. PostCSS

0 views0
Comments

Try It

Visit Website

Adoption

On StackShare

Companies
205
ATUOAR+199
Developers
805
ALSFMD+799