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

asset-compiler

v0.1.2

Published

A middleware for connect and union, that compiles and hosts assets (less.js, CoffeeScript, stylus).

Downloads

13

Readme

asset-compiler

This is meant to be a very simple asset compiler that helps speed up development. You add it as middleware in your development environment and it will compile and host all of your assets. This is not recommmended for use during production and it doesn't help you compile your assets for production- not the Rails asset pipeline.

hosting bootstrap

In this example we have a less file assets/css/style.less on disk that uses bootstrap. When the client requests 'assets/css/style.css' the asset compiler compiles style.less and serves the result.

var flatiron = require('flatiron'),
    union = require('union'),
    assetCompiler = require('asset-compiler'),
    app = flatiron.app;

app.use(flatiron.plugins.http, {
  before: [
    assetCompiler.middleware(__dirname, {
      css: ['/assets/css', '/vendor/bootstrap/less']
    })
  ]
});

adding a compiler (not complete)

Defining a compiler is fairly straight forward and the complete list is in an object called compilerMap because it maps file extensions to compilers. For example, css might map to a less compiler and a stylus compiler.

var less = require('less'),
    _ = require('underscore');

var getCompilerMap = function(root, assets) {
  return {
    css: {
      less: function(body, cb) {
        var parser = new less.Parser({
          paths: _.map(assets.css, function(path) { return root + path; })
        });
        return parser.parse(body, function(e, tree) {
          if (e) {
            cb(e);
            return;
          }
          cb(null, tree.toCSS());
        });
      }
    }
  };
};

I plan to make it easy to override and add new compilers, but the functionality isn't quite there yet. If you add it feel free to submit a pull request.