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

unpm-www

v1.8.0

Published

web frontend for unpm

Downloads

66

Readme

μnpm-www

a web frontend for npm-like registries (like μnpm)

installation

npm install -g unpm-www

usage

unpm-www

  • --port, -p <port> Listen on <port>, defaults to 8999
  • --registry, -r <registry> Use <registry> for package data, defaults to 'http://localhost:8123'
  • --static, -s <dir> Use files in <dir> to override static files when serving requests. (will fall back to defaults as necessary)
  • --title, -t <title> Title the page <title>, defaults to "unpm"
  • --version, -v Print version information
  • --help, -h Print help text

as a module

yep, you can do that:

var www = require('unpm-www')

var server = www('http://registry.npmjs.org')
server.listen(8999) // tada!

api

unpm_www(registry, prefix, title, static) -> httpServer

  • registry is the location of the npm-like registry you wish to use for package data, default is 'http://localhost:8123'
  • prefix will put all routes behind that given prefix
  • title is simply the title for the page header, default is 'unpm'
  • static is a directory with files to override static files

extending

you are given access to the router for you to add your own routes if you would like. or override them.

router is an instance of unpm-router, which works pretty much like you would expect a router to.

something like this:

var www = require('unpm-www')

var router = www.router

router.add('get', '/ping', ping)

function ping(req, res, route, config) {
  res.end('pong')
}

www().listen(1337)
  • route holds information like routes
  • config is a configuration object, currently with keys: "registry" and "prefix" (as explained above)

notes

works with any npm-compatible registry.

license

MIT