Alternatives to PurifyCSS logo

Alternatives to PurifyCSS

Sass, Animate.css , Less, PostCSS, and Stylus are the most popular alternatives and competitors to PurifyCSS.
12
23
+ 1
0

What is PurifyCSS and what are its top alternatives?

Remove unused CSS. Also works with single-page apps.
PurifyCSS is a tool in the CSS Pre-processors / Extensions category of a tech stack.
PurifyCSS is an open source tool with 9.8K GitHub stars and 419 GitHub forks. Here’s a link to PurifyCSS's open source repository on GitHub

Top Alternatives to PurifyCSS

  • 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. ...

  • 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. ...

  • Compass

    Compass

    The compass core framework is a design-agnostic framework that provides common code that would otherwise be duplicated across other frameworks and extensions. ...

  • 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. ...

  • Bourbon

    Bourbon

    Bourbon is a library of pure sass mixins that are designed to be simple and easy to use. No configuration required. The mixins aim to be as vanilla as possible, meaning they should be as close to the original CSS syntax as possible. ...

PurifyCSS alternatives & related posts

Sass logo

Sass

31.2K
23K
3K
Syntactically Awesome Style Sheets
31.2K
23K
+ 1
3K
PROS OF SASS
  • 608
    Variables
  • 593
    Mixins
  • 467
    Nested rules
  • 411
    Maintainable
  • 299
    Functions
  • 150
    Modular flexible code
  • 141
    Open source
  • 112
    Selector inheritance
  • 107
    Dynamic
  • 96
    Better than cs
  • 4
    Used by Bootstrap
  • 2
    If and for function
  • 1
    Better than less
  • 1
    Inheritance (@extend)
  • 1
    Custom functions
CONS OF SASS
  • 1
    Needs to be compiled

related Sass posts

Islam Diab
Full-stack Developer at Freelancer · | 9 upvotes · 31.5K views

Hi, I want to start freelancing, I have two years of experience in web development, and my skills in web development: HTML CSS JavaScript [basic, Object-Oriented Programming, Document object model, and browser object model] jQuery Bootstrap 3, 4 Pre-processor -> Sass Template Engine with Pug.js Task Runner with Gulp.js and Webpack Ajax JSON JavaScript Unit testing with jest framework Vue.js

Node.js [Just basic]

My Skills in Back end development Php [Basic, and Object-Oriented Programming] Database management system with MySql for database relationships and MongoDB for database non-relationships architecture pattern with MVC concept concept of SOLID Unit testing with PHPUnit Restful API

Laravel Framework

and version control with GitHub ultimately, I want to start working as a freelancer full time. Thanks.

See more

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 #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.

See more
Animate.css  logo

Animate.css

9.3K
1.6K
0
A library of CSS animations
9.3K
1.6K
+ 1
0
PROS OF ANIMATE.CSS
    Be the first to leave a pro
    CONS OF ANIMATE.CSS
      Be the first to leave a con

      related Animate.css posts

      Less logo

      Less

      1.9K
      1.1K
      931
      The dynamic stylesheet language
      1.9K
      1.1K
      + 1
      931
      PROS OF LESS
      • 215
        Better than css
      • 177
        Variables
      • 141
        Mixins
      • 99
        Maintainable
      • 79
        Used by bootstrap
      • 56
        Open source
      • 51
        Extendable
      • 43
        Functions
      • 39
        Dynamic
      • 30
        Fast
      • 1
        CSS is valid LESS, very easy to pick up
      CONS OF LESS
        Be the first to leave a con

        related Less posts

        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 #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.

        See more
        Julien DeFrance
        Principal Software Engineer at Tophatter · | 6 upvotes · 89.2K views
        Shared insights
        on
        BootstrapBootstrapLessLessSassSass
        at

        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.

        See more
        PostCSS logo

        PostCSS

        519
        457
        50
        Transform CSS with JS plugins
        519
        457
        + 1
        50
        PROS OF POSTCSS
        • 21
          The "babel" of CSS
        • 15
          Customizable
        • 8
          Autoprefixer
        • 2
          Variables
        • 1
          PostCSS Flexbugs Fixes
        • 1
          0
        • 1
          Mixins
        • 1
          CSS MQPacker
        CONS OF POSTCSS
          Be the first to leave a con

          related PostCSS posts

          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 #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.

          See more
          awesomebanana2018
          Shared insights
          on
          PostCSSPostCSSStylusStylusSassSass

          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
          Stylus logo

          Stylus

          375
          380
          331
          Expressive, robust, feature-rich CSS language built for nodejs
          375
          380
          + 1
          331
          PROS OF STYLUS
          • 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
          CONS OF STYLUS
            Be the first to leave a con

            related Stylus posts

            awesomebanana2018
            Shared insights
            on
            PostCSSPostCSSStylusStylusSassSass

            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
            Compass logo

            Compass

            338
            269
            12
            A Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain
            338
            269
            + 1
            12
            PROS OF COMPASS
            • 9
              No vendor prefix CSS pain
            • 1
              Mixins
            • 1
              Variables
            • 1
              Compass sprites
            CONS OF COMPASS
              Be the first to leave a con

              related Compass posts

              Autoprefixer logo

              Autoprefixer

              267
              37
              0
              PostCSS plugin to parse CSS and add vendor prefixes to CSS rules
              267
              37
              + 1
              0
              PROS OF AUTOPREFIXER
                Be the first to leave a pro
                CONS OF AUTOPREFIXER
                  Be the first to leave a con

                  related Autoprefixer posts

                  Bourbon logo

                  Bourbon

                  125
                  107
                  20
                  A lightweight mixin library for Sass
                  125
                  107
                  + 1
                  20
                  PROS OF BOURBON
                  • 14
                    Simple mixins
                  • 3
                    Lightweight
                  • 3
                    No javascript
                  CONS OF BOURBON
                    Be the first to leave a con

                    related Bourbon posts