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

grunt-task-rerun

v0.0.1

Published

Launch, relaunch and stop grunt task.

Downloads

3

Readme

grunt-task-rerun Build Status

Launch, relaunch and stop grunt task.

Getting Started

This plugin requires Grunt ~0.4.0

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-rerun --save-dev

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

grunt.loadNpmTasks('grunt-rerun');

The "rerun" task

Overview

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

grunt.initConfig({
  rerun: {
      yourtarget: {
        options: {
          tasks: ['express'],
          keepalive: false,
          port: 12456
        },
      },
    },
})

Options

options.task

Type: Array Default value: []

An array of grunt task to be 're-run'. Those should be long-living grunt task (like testacular server, express with keepalive and so on)

options.keepalive

Type: Boolean Default value: false

Wheter or not the rerun task should block or not. The preferred way is to leave keepalive to false and to useit in conjunction with other long-living task like watch

options.port

Type: Number Default value: 1247

The default port used for internal communication. The rerun:target task will launch a server listening on this port, wich will recive further comunication via the rerun:target:task:go task.

Usage Examples

In this example, the default options are used to so keepalive will be false and the port used internally will be 1247. So if the testing file has the content Testing and the 123 file had the content 1 2 3, the generated result would be Testing, 1 2 3.

grunt.initConfig({
  watch: {
      dev: {
        files: ['server/*.js'],

        //Note the :go flag used for sending the reload message to the rerun server
        tasks: ['clean','rerun:dev:express:go']
      },
    },
    express: {
        dev: {
            options: {
                port: 3000,
                bases: ['/public'],
                keepalive: true,
                server: path.resolve('./server/app.js')
            }
        }
    },
    // Configuration to be run (and then tested).
    rerun: {
      dev: {
        options: {
          tasks: ['express']
        },
      },
    }
})

Contributing

The project is in very ealry stage, so any suggestion, pull request and issue are welcomed. Please use github for any communication

Release History

(Nothing yet)