npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

postsass

v1.0.0

Published

Compile scss/sass files via sass and postcss from cli

Downloads

44

Readme

Powered by Tanuel Documentation npm npm

PostSass - Sass x PostCSS cli compiler

PostSass is a cli tool to build scss files via dart-sass and PostCSS

Installation

Requirements:

  • Node 12.x (Not tested for older versions)
  • yarn or npm

Using yarn

yarn add -D postsass

Using npm

npm install postsass --save-dev

Usage

PostSass will compile all .sass and .scss files to css, except partials starting with _, according to sass spec.

Basic

# compile files in the same directory
yarn postsass --dir src

# compile files from src to dist (keeping directory structure
yarn postsass --dir scss:css

#compile multiple directories
yarn postsass --dir scss:css --dir fonts
# -> write files from directory scss to css
# -> write files from directory fonts to fonts

Cli options

| Option | Values | Description | | ------------------------------------ | -------------------------- | -------------------------------------------------------------------------------------------------------------- | | --help | - | Show overview of commands | | --version | - | Show version | | --dir-d | - | Read files from source and write them to the destination if specified e.g. --dir src or --dir src:dist | | --outputStyle--style-s | compressed or expanded | output style according to dart sass | | --sourceMap | true or false | generate sourcemaps | | --context | default: process.cwd() | The working directory where to look for source files. Needs to be an absolute path | | --watch | - | Enable watch mode |

Configuration File and Postcss Plugins

You can provide a file named postsass.config.js to provide configuration and plugins for PostCSS

The file needs to be located in the working directory (process.cwd())

Example

const path = require("path");
const autoprefixer = require("autoprefixer");
const oldie = require("oldie");
const postcssUrl = require("postcss-url");

module.exports = {
  sass: {
    includePaths: [path.dirname(require.resolve("modern-normalize"))],
  },
  postcss: {
    plugins: [
      autoprefixer({ grid: "autoplace" }),
      oldie({
        rgba: {
          filter: true,
        },
      }),
    ],
    // when using the "use" property, you can pass callbacks to configure plugins at compile time
    // "from" gives you the source filename
    // "to" gives you the destination filename
    use: [
      // example: inline svg files, resolve relatively to file
      ({ from, to }) => postcssUrl({ filter: /\.svg$/, url: "inline", basePath: path.dirname(from) }),
    ],
  },
};

Why not postcss.config.js?

We do not want to conflict with other configuration files. This would give us limitations and we would have to be aware of compatibility issues. Postsass is not intended to be used along postcss-cli or webpack or any other compiler tools, but is aimed to work standalone for those who don't use a bundler