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

postcss-processor-order

v0.1.1

Published

PostCSS plugin for sorting processors passed to postcss

Downloads

5

Readme

PostCSS Processor Order Build Status

PostCSS plugin for sorting processors passed to postcss.

Because you really want to forget about plugins priority and add processors in any order. You want to write CSS but not think how to built your preprocessor from the bricks. The only requirement that this plugin should be first processor passed to PostCSS.

/* Input example */
require('postcss-processor-order')(),
require('postcss-each')(),
require('postcss-inline-svg')(),
require('stylelint')(),
require('postcss-nested')(),
require('postcss-partial-import')(),
require('postcss-svgo')(),
/* Output example */
require('postcss-processor-order')(),
require('postcss-partial-import')(),
require('postcss-each')(),
require('postcss-nested')(),
require('postcss-inline-svg')(),
require('postcss-svgo')(),
require('stylelint')()

Install

npm i postcss-processor-order --save

Usage

postcss([ require('postcss-processor-order')(opts) ])

See PostCSS docs for examples for your environment.

Options

  • order {Array} priority of plugins. By default it uses params from config.js

Contributing

There are a lot of PostCSS plugins and, I'm sure, you even not aware about half of them. I'm extending this priority list with plugins when I reach them in my code.

So, if you faster than me, please, send me your PR with modified version of config.js where you add new plugins.

Don't forget to run npm test before commit.