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-npm-view

v0.1.0

Published

express middleware to lookup npm package data

Downloads

3

Readme

express-npm-view

Not ready for primetime yet!

Build Status

Express middleware to lookup npm package data.

How?

Unfortunately, due to the npm api, middleware initialize() needs to be async.

npm install express-npm-view. Then use it, like one of these examples:

var npmView = require('express-npm-view');

npmView.initialize(function (err) {
    app.use(npmView({
        fields: ["name"]
    });
    
    app.get("/package/:package", function (req, res) {
        res.send(req.npm);
    });
});
var npmView = require('express-npm-view');

npmView.initialize({ fields: ["name"] }, function (err) {
    app.get("/package/:package", npmView(), function (req, res) {
        res.send(req.npm);
    });
    
    app.get("/module/:module", npmView({ queryProperty: "module" }), function (req, res) {
        res.send(req.npm);
    });
});

API

initialize({}, cb)

Async setup things. This is needed because we need to call npm.load which is async.

Optionally pass a configuration object (below are their default values):

{
    fields: [], // the fields we lookup, these get passed to npm.commands.view
    queryProperty: "package", // the property we get the package name from
    propertyName: "npm", // the property we export the data on
    npmOptions: {} // these get passed to npm.load
}

queryProperty is a bit tricker than the rest - it's not immediately clear where we lookup this property, so i'm calling it out explicitly. We first try req.params[queryProperty], then req.query[queryProperty] and finally req.body[queryProperty]. If we still haven't found it, we fail silently (that means they'll be no impact to your app, other than req[propertyName] won't be set).

Pass a callback function (cb) that will be called with err if there's an error. Otherwise it's called with nothing, when everything is setup.

({})

This is the middleware provider. Optionally pass a configuration object with any of the options documented above in initialize() (with the exception of npmOptions). Any options passed here override options passed to initialize().

It will return a middleware function (that is, something that matches the (req, res, next) signature) that you can app.use.