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 🙏

© 2026 – Pkg Stats / Ryan Hefner

express-jam

v0.0.1

Published

Respects `NODE_ENV` environment parameter of Express, it returns a single catalog with all dependencies in production, but each dependency in its own file in development mode. Development mode does not need server restart if dependencies change.

Readme

ExpressJS and JamJS work together

Respects NODE_ENV environment parameter of Express, it returns a single catalog with all dependencies in production, but each dependency in its own file in development mode. Development mode does not need server restart if dependencies change.

Respects packageDir property from package.json.

Configure dependencies

Write dependencies in package.json and execute express-jam-install script on installation:

{
  "scripts": {
    "postinstall": "env PATH=./node_modules/.bin:$PATH express-jam-install"
  }
  ,"jam": {
    "dependencies": {
      "jquery": "1.8.0"
    }
  }
}

See Jam documentation for more details.

Link to an express app

var app = require('express')()

linkJam(app, function(error) {
  if (error) {
    console.log(error);
    process.exit(1);
  } else {
    app.listen(3000);
  }
});

Use in views

The uri to jam bootstrap is provided to views in view options, by default in key jam_uri. For example in jade:

!!!
html
  head
    title Jam-Express
    script(type='text/javascript', src='#{jam_uri}', data-main='index')
  body
    p Hello, world!

Use out of views

The middleware returned can be used to expose the variable in response:

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

linkJam(app, function(error, middleware) {
  if (error) {
    console.log(error);
    process.exit(1);
  } else {
    app.get('/', middleware, function(req, res) {
      res.send('Hello at: ' + req.jam_uri);
    });
    app.listen(3000);
  }
});

Environment parameters

  • process.env.JAM_VIEW_KEY (defaults to jam_uri): key in views options that holds the uri to jam bootstrap

Licence

MIT, see license.txt.