PostCSS聽vs聽Sass聽vs聽Stylus

Need advice about which tool to choose?Ask the StackShare community!

PostCSS

472
416
+ 1
49
Sass

26.5K
19K
+ 1
3K
Stylus

371
367
+ 1
331
Advice on PostCSS, Sass, and Stylus
awesomebanana2018
Needs advice
on
Stylus
Sass
and
PostCSS

Originally, I was going to start using Sass with Parcel, but then I learned about Stylus, which looked interesting because it can get the property values of something directly instead of through variables, and PostCSS, which looked interesting because you can customize your Pre/Post-processing. Which tool would you recommend?

See more
Replies (1)
Recommends
PostCSS

You're not correct with saying "vs Postcss". You're using Less/Sass/Stylus/... to produce "CSS" (maybe extended means it has some future features) and then in any case PostCSS will play (it is shipped with Parcel/NextJS/CRA/...)

See more
Decisions about PostCSS, Sass, and Stylus
Cory Bell

JSS is makes a lot of sense when styling React components and styled-components is a really nice implementation of JSS. I still get to write pure CSS, but in a more componentized way. With CSS post-processors like SASS and LESS, you spend a lot of time deciding where your .scss or .less files belong, which classes should be shared, and generally fighting the component nature of React. With styled-components, you get the best of CSS and React. In this project, I have ZERO CSS files or global CSS classes and I leverage mixins quite a bit.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of PostCSS
Pros of Sass
Pros of Stylus
  • 20
    The "babel" of CSS
  • 15
    Customizable
  • 8
    Autoprefixer
  • 2
    Variables
  • 1
    PostCSS Flexbugs Fixes
  • 1
    0
  • 1
    Mixins
  • 1
    CSS MQPacker
  • 603
    Variables
  • 586
    Mixins
  • 464
    Nested rules
  • 411
    Maintainable
  • 296
    Functions
  • 148
    Modular flexible code
  • 140
    Open source
  • 111
    Selector inheritance
  • 107
    Dynamic
  • 96
    Better than cs
  • 4
    Used by Bootstrap
  • 2
    If and for function
  • 1
    Custom functions
  • 1
    Better than less
  • 69
    Simple
  • 54
    Indented syntax
  • 38
    Efficient
  • 33
    Built for node.js
  • 32
    Open source
  • 24
    Expressive
  • 21
    Maintainable
  • 17
    Feature-rich
  • 13
    Better than CS
  • 6
    Variables
  • 5
    Functions
  • 3
    @extend directive
  • 2
    Contempt for curly brackets
  • 2
    Very clean
  • 2
    Mixins
  • 2
    Is Easy
  • 2
    No colons, semi-colons or even curly braces
  • 1
    Its unique
  • 1
    Dynamic selectors
  • 1
    Scriptable
  • 1
    Easy Efficiently
  • 1
    Transparent
  • 1
    Supports orthogonal architecture

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

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.

What is 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.

What is 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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use PostCSS?
What companies use Sass?
What companies use Stylus?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with PostCSS?
What tools integrate with Sass?
What tools integrate with Stylus?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to PostCSS, Sass, and Stylus?
CSS Modules
It is a CSS file in which all class names and animation names are scoped locally by default. The key words here are scoped locally. With this, your CSS class names become similar to local variables in JavaScript. It goes into the compiler, and CSS comes out the other side.
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.
node-sass
It is a library that provides binding for Node.js to LibSass, the C version of the popular stylesheet preprocessor, Sass. It allows you to natively compile .scss files to css at incredible speed and automatically via a connect middleware.
styled-components
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 馃拝
Webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
See all alternatives
Reviews of PostCSS, Sass, and Stylus
Review of
Stylus

One of the main reasons I use it is that it combines most of what I like but is spread across other preprocessors.

The option to make functions that take places of properties is amazing. ie. border-radius: "child" $parent-radius can actually be calling a function like border-radius("child", $parent-radius) where using border-radius: 4px would just implement the standard expected result.

Add in my favorite selector: `^[-1..-1] to get the last raw selector in a nested situation. (its like magic in combination with BEM naming syntax)

How developers use PostCSS, Sass, and Stylus
Mick Dekkers uses
PostCSS

PostCSS essentially allows you to set up your own CSS preprocessor with the features that matter to you. It has a modular plugin-based architecture, which means that if someone comes up with a useful new feature, you can easily add it to your stack as a PostCSS plugin. PreCSS and PostCSS-cssnext are some of my go-to plugins.

Kevin Ard uses
Sass

It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.

Tim Lucas uses
PostCSS

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.

Climate CoLab uses
Sass

Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.

Ujjwal Bhujel uses
Sass

When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.

Scrayos UG (haftungsbeschr盲nkt) uses
Sass

Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.

Refractal uses
Sass

CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.

Virtually(Creative) uses
PostCSS

Used to minify and extend the CSS markup of the framework.

BookAuthority uses
PostCSS

We use PostCSS to improve cross-browser compatibility

LapNghiep uses
Stylus

Accompanied with ReactJS code

Sunny Singh uses
PostCSS

Compiles future CSS.

Thomas Hunsaker uses
Stylus

I hate CSS.