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-regexp-detect

v0.2.0

Published

PostCSS plugin to search for regexp in rule declarations

Downloads

3

Readme

postcss-regexp-detect

PostCSS plugin to search for regexp in rule declaraions

##Purpose This plugin was initially created to analyse css compiled by stylus and find unresolved variables.

When stylus can't resolve a variable, it inserts string with its name and doesn't throw any warning. To avoid such surprises we developed this warning plugin.

Usage

This plugin writes all warnings to postcss result.messages. You'll need some tool to handle them. You can process them manually, or use some plugin for output. for example, postcss-reporter.

// dependencies
var fs = require("fs")
var postcss = require("postcss")
var regexp = require("postcss-regexp")
var reporter = require('postcss-reporter');

// css to be processed
var css = fs.readFileSync("input.css", "utf8")

// process css
var output = postcss()
  .use(regexp({
      regexp: new RegExp('.+px'),
      messagePattern: 'Pixel value %s found on line %l'
  }))
  .use(reporter)
  .process(css, {
    from: "src/stylesheet/index.css"
    to: "dist/index.css"
  })
  .css

Options

regexp (required)

Type: String or RegExp

Regexp to match

messagePattern (optional)

Type: String Default: Regexp matched with %s on line %l

Pattern for message text.

  • %s is for matched strings
  • %l is for line number
  • %f is for postcss from parameter

License