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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-pid-file

v0.1.3

Published

Grunt tasks for pid file management

Readme

grunt-pid-file

Grunt tasks for pid file management

Travis-CI

Build Status

Getting Started

This plugin requires Grunt ~0.4.2

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-pid-file --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-pid-file');

The "pid-file" task

Overview

In your project's Gruntfile, add a section named pidFile to the data object passed into grunt.initConfig().

grunt.initConfig({
  pidFile: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.file

Type: String Default value: .tmp/pid-file.pid'

A file path that is created when the the task pidFile is ran and deleted when the grunt process exists.

options.killIfRunning

Type: Boolean Default value: false

If this value is false, and the pid file already exists when the task is ran, the pid file will be updated with the new pid. The previous process ID, if running or stopped, is ignored. If this value is ture, and the pid file already exists when the task is ran, the process ID in the pid file is read, and then killed with process.kill(pid);. Then the pid file is updated with the current grunt process.

Usage Examples

Default Options

In this example, running the pidFile task will create a pid file, and delete it when the process exits. If a long running process, such as grunt pidFile server is running, running grunt pidFile server again will leave the current server running and try to start a new one. The pid file will be updated with the new process id.

grunt.initConfig({
  pidFile: {
    options: {},
    // Defaults to 
    // file: './tmp/pid-file.pid'
    // killIfRunning : false
  },
});

Custom Options

A common use case for grunt-pid-file will be to start a grunt server, and kill it later. Another use case is to start a grunt server, and upon start, kill any previously running grunt servers, and then start a new one.

For example, you start a grunt server with grunt pidFile server which will run the grunt tasks pidFile (which will create the pid file) and then server (which starts a web server and runs forever/untill killed). Then some time later you start a second grunt process grunt pidFile server. This will kill the first server, and start a new one.

Another example, you start a grunt server with grunt pidFile server, which will run forever. Running simply grunt pidFile will kill the server.

grunt.initConfig({
  pidFile: {
    options: {
      killIfRunning : true,
    },
    myTask : {
      file : '.tmp/grunt-server.pid',
    },
  },
});

Contributing

Email me/tweet me!

Release History

(Nothing yet)