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

expressive

v1.0.4

Published

Adds environment-specific hooks to express apps

Downloads

3

Readme

Build Status downloads npm Code Climate Test Coverage dependencies

NPM info

Expressive

Installation

npm install --save expressive

Usage

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

// nconf setup not pictured
expressive(app, nconf.get('NODE_ENV')).env('development');

app.use('/normal-route', function(req, res, next) {
  next();
});

app.development.get('/dev-only-route', function(req, res, next) {
  next();
});

Expressive installs environment-specific hooks in your express app, which essentially eliminates the need to do something like

if (process.env.NODE_ENV === 'development') {
  app.use(/* some dev route */)
}

Of course, you could just use if statements like this, but I've found that expressive makes an app easier to read because all the route definitions are parallel. Additionally, testing is slightly easier because you don't have to specify a describe for each environment. You can just assert that app.environmentName exists and, if you're into this kind of thing, that it gets called with the appropriate routes and handlers.

Api

Expressive exports a single function that takes two arguments: your express app and, optionally, the current environment (defaulting to process.env.NODE_ENV). It returns an object with a single method: .env.

expressive(app)

or

expressive(app, currentEnvironment)

.env

The .env method also takes two arguments: the name of the environment to add hooks for and an optional alias for that environment. This method returns the same object (this) so you can chain your .env calls.

Example

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

expressive(app)
  .env('test')
  .env('smoktest')
  .env('development', 'dev') // Alias "dev" allows you to do app.dev.use instead of app.development.use

Contributing

Please see the contribution guidelines.