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

mincer-simple-server

v1.0.2

Published

Compile mincer assets with HTTP requests

Downloads

16

Readme

mincer-simple-server

Compile your mincer assets as fast as idiomatically possible—just a curl localhost away.

mincer-simple-server supports out of the box:

  • Source Maps
  • CoffeeScript
  • Haml Coffee Templates
  • Persistent assets caching on the filesystem, through Mincer.FileStore

Installation

$ npm install mincer-simple-server

Usage

Server

$ npm install
$ node serve.js --root /Users/randall/Workspace/project/ --include lib/assets/javascripts vendor/assets/javascripts --build_dir build --enable-source-maps --files application.js.coffee

Parameters:

  • --root (String): --include and --build-dir are calculated against this value. Required.
  • --include (yargs.array): Mincer load path directories. Required.
  • --build-dir (String): Assets/maps/mincer cache are all built here. Required.
  • --enable-source-maps (Boolean): Toggle source map generation on (at a performance hit). Optional, defaults to false.
  • --port (String): Port the server listens on. Optional, defaults to 3000.
  • --files (yargs.array): Files in the Mincer load path to be processed. Required.

The first compile of an asset with a lot of require calls will take a long time (~20s on a 2014 MacBook Pro) because a cache will be built to $build_dir/cache.

Client

To mince assets:

$ curl -X PUT localhost:3000

To kill the server:

$ curl localhost:3000/exit

Contributing :heart_eyes:

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Guidelines

  1. Keep things simple
  • The mincer API has support for a lot of features, including manifest files (to track asset hash changes) and built-in connect middleware...
  • ...but in lieu of using the aforementioned methods (Manifest.compile and Server.compile) to build assets, we call Environment.findAsset. It's a lower level method that spits out an Asset object in only one line, and it helps keep us out of callback hell.
  1. Run jshint before you submit anything upstream