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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vinylsmith

v1.0.0

Published

Process your Wintersmith contents with Gulp plugins

Readme

vinylsmith

Process your Wintersmith site with Gulp plugins.

Synopsis

vinylsmith = require 'vinylsmith'
stylus    = require 'gulp-stylus'
pleeease  = require 'gulp-pleeease'
rev       = require 'gulp-rev'

# In your custom plugin (see Usage for more details):
# Instead of writing your own ContentPlugin, use vinylsmith to generate them!
env.registerContentPlugin 'styles', '**/*.styl',
  vinylsmith(env)
    .pipe(stylus, 'include css': true)   # compile stylus
    .pipe(pleeease)                      # autoprefix, minify
    .pipe(rev)                           # asset-hashing

Background

Wintersmith is a nice static site generator, very extensible through plugins. The problem is that, as of writing, you cannot chain plugins together.

This means you can’t create plugins that do one thing, and one thing well. Instead, you have plugins that do several things, such as wintersmith-autoprefixer-sass and wintersmith-autoprefixer-less. Now I use Stylus and where is wintersmith-autoprefixer-stylus? No. You only have wintersmith-stylus.

Building web sites nowadays requires you to preprocess, compile, and postprocess your assets. Because of different needs and use cases, the combinations are infinite. We won’t get very far without composability. And hence, vinylsmith!

Usage

Install it:

npm install --save-dev vinylsmith

Create a Wintersmith plugin:

  "plugins": [
    "./plugins/bemuse.coffee"
  ],

Use vinylsmith in your plugin:

vinylsmith = require 'vinylsmith'

stylus    = require 'gulp-stylus'
pleeease  = require 'gulp-pleeease'
babel     = require 'gulp-babel'
uglify    = require 'gulp-uglify'
rev       = require 'gulp-rev'

module.exports = (env, callback) ->

  env.registerContentPlugin 'styles', '**/*.styl',
    vinylsmith(env)
      .pipe(stylus, 'include css': true)
      .pipe(pleeease)
      .pipe(rev)

  env.registerContentPlugin 'scripts', '**/*.js',
    vinylsmith(env)
      .pipe(babel, experimental: true)
      .pipe(uglify)
      .pipe(rev)

  callback()

Note: Don't call the plugin function! vinylsmith will call it for you. See also: lazypipe.

Note: Your Gulp plugin pipeline must emit only one file! This is by design, because Wintersmith assumes 1-to-1 mapping from content files to output files.

Disclaimers

  • I wrote and maintain this package for use in my own projects.
  • Therefore, if you find issues with this package, please don’t expect me to fix it. This package’s code is less than 100 lines, and you are encouraged to fix it. Pull requests are welcome.
  • There are no tests, but it worked pretty well for my project. If you feel the need for one, feel free to write one! Again, pull requests are welcome. :smiley: