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

express-lazy

v1.1.1

Published

Extends express with a .lazy(pathname, createHandler), analogous to .use(pathname, handler), for instant-on servers.

Downloads

13

Readme

express-lazy

Extends express 4.x with lazy methods, for instant-on servers (particularly on embedded devices).

Instead of loading and processing all of the requires for your apps all at once, you can wait until the route is used and load the middleware (nearly) instantly at that time.

This pattern will produce a server that is ready to handle requests much quicker than traditional means.

  • .lazy(createHandler);
  • .lazy(mountname, createHandler);
  • .lazyMatch(mountname, routePrefix, createHandler);

Usage

'use strict';

var express = require('express-lazy');
var query = require('connect-query');
var app = express();

app.use(query());

// Calls .use(pathname, handler) under the hood
app.lazy('/api/texter', function () {
  var urlrouter = require('urlrouter');
  var mySmsHandler = require('./my-sms-handler');
  return urlrouter(mySmsHandler);
});

// Calls .use('/api', handler) and manually checks that the remaining route prefix matches
app.lazyMatch('/api', '/webhooks/email', function () {
  return require('./my-email-handler').create({ foo: 'bar'}).then(function (mailRestApi) {
    var urlrouter = require('urlrouter');
    return urlrouter(mailRestApi);
  });
});

app.use(express.static(__dirname + '/public'));

return app;

Note that you can return a route handling function or a promise;

Alternate Usage

'use strict';

var express = require('express');
var lazify = require('express-lazy');
var app = express();

lazify.inject(app);

// ...