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
Sass
BySassSass

Sass

#1in Templating Languages & Extensions
Discussions81
Followers32.2k
OverviewDiscussions81

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.

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

Sass Pros & Cons

Pros of Sass

  • ✓Variables
  • ✓Mixins
  • ✓Nested rules
  • ✓Maintainable
  • ✓Functions
  • ✓Modular flexible code
  • ✓Open source
  • ✓Selector inheritance
  • ✓Dynamic
  • ✓Better than cs

Cons of Sass

  • ✗Needs to be compiled

Sass Alternatives & Comparisons

What are some alternatives to Sass?

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.

PostCSS

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.

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.

Sass Integrations

Compass, Bourbon, Toolkit, Jolteon, Bootstrap.build and 7 more are some of the popular tools that integrate with Sass. Here's a list of all 12 tools that integrate with Sass.

Compass
Compass
Bourbon
Bourbon
Toolkit
Toolkit
Jolteon
Jolteon
Bootstrap.build
Bootstrap.build
Ember-cli
Ember-cli
node-sass
node-sass
JSFiddle
JSFiddle
Vertica
Vertica
Chartist.js
Chartist.js
Can I email
Can I email
Lad
Lad

Sass Discussions

Discover why developers choose Sass. Read real-world technical decisions and stack choices from the StackShare community.Showing 4 of 5 discussions.

Julien DeFrance
Julien DeFrance

Principal Software Engineer at SmartZip

Feb 24, 2019

Needs adviceonBootstrapBootstrapLessLessSassSass

Which #GridFramework to use? My team and I closed on Bootstrap !

On a related note and as far as #stylesheets go, we had to chose between #CSS, #SCSS, #Sass , Less Finally opted for Sass

As syntactically awesome as the name announces it.

0 views0
Comments
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
Russel Werner
Russel Werner

Lead Engineer at StackShare

Sep 13, 2018

Needs adviceonSassSassHAMLHAMLReactReact

When we rebooted our front-end stack earlier this year, we wanted to have a consolidated and friendly developer experience. Up to that point we were using Sass and BEM. There was a mix of HAML views, React components and Angular. Since our ongoing development was going to be exclusively in React, we wanted to shift to an inline styling library so the "wall of classnames" could be eliminated. The ever-shifting landscape of inline CSS libraries for React is sometimes difficult to navigate.

We decided to go with Glamorous for a few reasons:

  1. Previous team experience with this library
  2. We can write our styles in plain @{JavaScript}|tool:1209| (which brings many benefits)
  3. It supports server-side rendering
  4. It has great composition patterns

As you may or may not know, Glamorous has ceased active development and been mostly superseded by Emotion. We are planning to migrate to either Emotion or @styled-components in the near future, and I'll write another Stack Decision when we get there!

#inlinecss

0 views0
Comments
View all 5 discussions

Try It

Visit Website

Adoption

On StackShare

Companies
4.38k
AAACTD+4370
Developers
37.3k
NMPBSL+37305