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-igdeploy

v1.1.0

Published

Grunt task for the FT's igdeploy module

Readme

grunt-igdeploy

A grunt task to deploy to the FTI static content server. (Intended for internal FT use; may or may not work on your server.)

Basic usage

npm install --save-dev grunt-igdeploy
grunt.loadNpmTasks('grunt-igdeploy');

grunt.initConfig({
  igdeploy: {
    options: {
      src: 'dist',
      host: 'example.com',
      destPrefix: '/some/long/path/to/your/web/root'
    },

    staging: {
      options: {
        dest: 'your/staging/dir'
      }
    },

    production: {
      options: {
        dest: 'your/prod/dir'
      }
    }
  }
})

The destPrefix option will be used as the base for the dest option, i.e. path.join(options.destPrefix, options.dest). (Exception: if any target's dest begins with a /, that dest will be considered absolute, and will not be prefixed with the destPrefix.)

You should also create a file named .igdeploy in the following format:

{
  "username": "John.Smith",
  "password": "kittenz"
}

You can put your .igdeploy in any ascendant directory of your project, eg, your home directory. (Or you can put it directly in your project directory, but be careful not to commit it.)

The contents of your .igdeploy file will be merged into the options passed to igdeploy. (But options specified in your gruntfile take priority). You can put any sensitive options in your .igdeploy file if you don't want to commit them. Note the options from .igdeploy are merged in after Grunt has resolved the options object for whatever target you're running – so you can't put target-specific options in the .igdeploy file.

Running it

Then run: grunt igdeploy:staging.

In the above example, this would upload ./dist to /some/long/path/to/your/web/root/foo/staging on example.com.

If the target directory already exists, it will be renamed with __IGDEPLOY_OLD after it.

If you set the option undo: true, this will put igdeploy into 'undo mode'. This means it doesn't upload anything; instead it just looks for the [yourpath]__IGDEPLOY_OLD folder and swaps it with the [yourpath] folder. So you only get one chance to undo – subsequent runs will just undo the undo. Like Photoshop.