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 🙏

© 2025 – Pkg Stats / Ryan Hefner

npm-dev

v0.0.0

Published

Run your node.js server and automatically restart if needed.

Downloads

71

Readme

npm-dev -- Develop Server for NPM

Run your node.js server and automatically restart if needed.

Introduction

This project is inspired by gulp-develop-server, but with some important differences:

  • Zero configuration in most use cases
  • Provide npm-dev cli
  • Spawn in a separate process group so all child processes can be cleanly killed
  • Better APIs (in my opinion :)
  • Written in ES6+

Usage as a global tool

Install

npm install npm-dev --global

Just run npm-dev under your project directory.

Local configuration

Edit .npmdevrc

Usage as a local package

Install

npm install npm-dev --save-dev

APIs

import {Server} from 'npm-dev'

const serv = new Server()

serv.watch('lib/**/*.js')

Gulp Sample

import {Server} from 'npm-dev'

const serv = new Server()

gulp.task('start', () => {
	serv.start()
})

gulp.task('dev', () => {
	gulp.watch('lib/**/*.js', () => {
		serv.restart()
	})
})