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

@gebruederheitz/postcss-pkg-version-to-stylesheet

v1.0.0

Published

PostCSS plugin to replace a template string in your stylesheet with your current package version from package.json

Downloads

2

Readme

PostCSS Pkg Version To Stylesheet

PostCSS plugin to replace a template string in your stylesheet with your current package version from package.json.

Input

/*!
    Theme Name: my-wordpress-theme
    Theme URI: https://github.com/user/theme
    Author: you
    Author URI: https://example.com
    Description: My Fance Wordpress Theme
    Requires at least: WordPress 5.8.1
    Version: {{ package_version }}
    License: private
*/
.foo {
    color: hotpink;
}
// package.json
{
  "name": "my-wordpress-theme",
  "version": "1.8.2"
}

Output

/*!
    Theme Name: my-wordpress-theme
    Theme URI: https://github.com/user/theme
    Author: you
    Author URI: https://example.com
    Description: My Fance Wordpress Theme
    Requires at least: WordPress 5.8.1
    Version: 1.8.2
    License: private
*/
.foo {
  color: hotpink;
}

Usage

Step 1: Install plugin:

npm i -D postcss @gebruederheitz/postcss-pkg-version-to-stylesheet

Step 2: Check you project for existed PostCSS config: postcss.config.js in the project root, "postcss" section in package.json or postcss in bundle config.

If you do not use PostCSS, add it according to official docs and set this plugin in settings.

Step 3: Add the plugin to plugins list:

module.exports = {
  plugins: [
+   require('@gebruederheitz/postcss-pkg-version-to-stylesheet'),
    require('autoprefixer')
  ]
}

Options

By default this plugin will use the package.json located at the current working directory (i.e. wherever you (or your task runner) are running postcss from). You can provide an alternative package.json through the packagePath option as a string.