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

transform

v1.1.2

Published

The ultimate transformation/build/compilation middleware/command line/etc. system for node.js

Downloads

8,308

Readme

transform

The ultimate transformation/build/compilation middleware/command line/etc. system for node.js

Installation

$ npm install transform

Basic Usage

The following example compiles coffe-script to JavaScript files and minifies all JavaScript files (including those generated by coffee-script in the previous step). To run this sample you will need to also install coffee-script and uglify-js (npm install coffee-script uglify-js)

var express = require('express');
var app = express();

var path = require('path');

var transform = require('transform');

app.use(transform(path.join(__dirname, 'source'))
        .using(function (transform) {
          transform.add('.jade', '.html', 'jade');

          //It's OK to have multiple formats that all result in the same extension
          //only one will be active per file though
          transform.add('.less', '.css', 'less');
          transform.add('.styl', '.css', 'stylus');
          transform.add('.sass', '.css', 'sass');

          //these files will first be transformed by coffee-script and then by
          //uglify-js if enabled bellow.
          transform.add('.coffee', '.js', 'coffee-script', {bare: true});

          //we can easilly set it up to only minify in production
          if (process.env.NODE_ENV && process.env.NODE_ENV != 'development')
            transform.add('.js', '.js', 'uglify');
        })
        .to(path.join(__dirname, 'destination')));


app.listen(3000);

The code for .to is:

function (destination) {
  if (process.env.NODE_ENV && process.env.NODE_ENV != 'development') {
    return this.statically(destination);
  } else {
    return this.dynamically();
  }
}

Calling .statically(destination) compiles the files to physical files in destination and then serves them using connect's static middleware.

Calling .dynamically() returns middleware that compiles each file every time they are requested.

License

MIT