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

exit-on-changes

v0.1.2

Published

Exit a node/io.js process when changes to source files in the current directory are detected

Downloads

10

Readme

exit-on-changes

NPM version

exit-on-changes quits your node/io.js program when changes to source files are detected, leaving the parent process or shell to actually start it again. This avoids some of the problems with other solutions that must spawn two io.js processes or prevent you from using your shell aliases. exit-on-changes is particularly useful (vs. the alternatives) in Cygwin environments, but works elsewhere too.

Install

In your project, run:

npm install exit-on-changes --save

or install from the GitHub repo:

npm install ludios/exit-on-changes --save

API

Somewhere in your program:

require('exit-on-changes');

Then start your program with the environmental variable EXIT_ON_CHANGES_ENABLED=1.

This will exit on changes to source files in the current directory. To actually have the program restart in a loop, use this restarter() function for zsh, or write a similar loop.

Example:

restarter EXIT_ON_CHANGES_ENABLED=1 iojs app.js