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

metalsmith-branch

v0.0.5

Published

A metalsmith plugin to run separate middleware pipelines on selected files

Downloads

94

Readme

metalsmith-branch

A metalsmith plugin to run separate middleware pipelines on selected files.

Facilitates 'declarative' pipelines by file pattern or filter, since it means each plugin doesn't have to implement its own filtering. See examples below.

April 2014: Please bear in mind that this is 0.0.x software and use with caution, especially since metalsmith itself is likely to change.

Installation

$ npm install metalsmith-branch

Usage

In your build file:

var branch = require('metalsmith-branch')

metalsmith
  .use( branch()
          .pattern('*.md')        // for only md source files,
          .use( templates({       // run through swig template engine
                  engine: "swig",
                  inPlace: true
                })
          )
          .use( markdown() )      // and generate html
      )

// you can also specify the pattern directly in constructor

metalsmith
  .use( branch('images/*') 
          .use( imageVariants() )
      )

// or select files by function of their name, properties, and order:

var lastweek = function(filename,props,i){
  var dt = new Date()
    , last = new Date( dt.getFullYear(), dt.getMonth(), dt.getDate());
  last.setDate( last.getDate() - 6 )
  return ( props.published >= last );
}

metalsmith
  .use( branch( lastweek )
          .use( tagLatest() )
      )

Note that nested branches are possible too.

// to post-process only markdown-sourced files in a 'special' dir:

metalsmith
  .use( branch('*.md')
          .use( markdown() )
          .use( branch('special/*.html')
                  .use( postProcess() )
              )
      )

It's also possible to specify an array of patterns:

// to select all markdown files in the "posts" and "projects" directories:

metalsmith
  .use( branch()
          .pattern(["projects/*/*.md", "posts/**/*.md"])
          .use( markdown() )
      )

See multimatch for all pattern options.

License

MIT