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

shipit-captain

v0.4.4

Published

Shipit task running wrapper

Downloads

216

Readme

shipit-captain

Run Shipit tasks from Gulp, or any task runner. Includes Inquirer.js prompts, CLI arguments, customized logging, and more.

shipit-captain demo

Why?

Shipit comes with its own CLI, but I wanted to integrate Shipit tasks into our existing task workflow, be it Gulp, Grunt, or anything else.

shipit-captain will let you easily do things like set default environments, log confirmation prompts, and easily integrate into Gulp tasks.

Install

$ npm install --save shipit-captain

Usage

You can organize your config files any way you like. Below is my preference, as it still allows shipit-cli commands to work, as well as those intended for shipit-captain. The only requirement is you must separate your shipit.config exports.

Example shipitfile.js

module.exports = require('./config/shipit').init;

Example config/shipit.js

var config = {
  default: {
    workspace: '/tmp/github-monitor',
    deployTo: '/tmp/deploy_to',
    repositoryUrl: 'https://github.com/user/repo.git',
    ignores: ['.git', 'node_modules'],
    keepReleases: 2,
    deleteOnRollback: false,
    key: '/path/to/key',
    shallowClone: true
  },
  staging: {
    servers: '[email protected]'
  }
};
module.exports.config = config;
module.exports.init = function(shipit) {
  require('shipit-shared')(shipit);
  shipit.initConfig(config);
}

Example gulpfile.js

var gulp = require('gulp');
var shipitCaptain = require('shipit-captain');

// With no options, will run shipit-deploy task by default.
gulp.task('shipit', function(cb) {
  shipitCaptain(shipitConfig, cb);
});

// Run other after Shipit tasks are completed 
gulp.task('myTask', ['shipit'], function(cb) {
  console.log('Shipit tasks are done!');
  cb();
});

// Pass options 
var options = {
  init: require('config/shipit').init,
  run: ['deploy', 'clean'],
  targetEnv: 'staging',
}

gulp.task('deploy', function(cb) {
  shipitCaptain(shipitConfig, options, cb);
});
// 

API

captain(shipitConfig, [options], [cb])


shipitConfig

@param {object} shipitConfig

The config object you would normally pass to shipit.initConfig.

Gulp example:
gulp shipit -e production

options.run

@param {string|string[]} [options.run=[]]

A string or array of strings of Shipit tasks to run. If not set, user will be prompted for a task to run from all available tasks.

Users may set options.run manually, or by passing the -r or --run argument via the CLI. If set via CLI, comma-separate multiple tasks names.

Gulp example:
gulp shipit --run deploy,myOtherTask

options.availableEnvs

@param {string[]} [options.availableEnvs]

By default this will be set to any environments defined in shipitConfig. This shouldn't normally need to be set.


options.confirm

@param {boolean} [options.confirm=true]

Set to false to bypass the confirmation prompt.


options.logItems

{function} [options.logItems(options, shipit)]

Gulp example:
var options = {
  logItems: function(options, shipit) {
    return {
      'Environment': options.targetEnv,
      'Branch': shipit.config.branch,
    };
  },
};

gulp.task('shipit', function(cb) {
  shipitCaptain(shipitConfig, options, cb);
});

options.init

{function} [options.init(shipit)]

Require Shipit plugins or anything else you would have in your shipitfile.

shipit.initConfig will be called automatically if it has not already been called.

Gulp example:
var options = {
  init: function(options, shipit) {
    require('shipit-deploy')(shipit);
    require('shipit-shared')(shipit);
  }
};

gulp.task('shipit', function(cb) {
  shipitCaptain(shipitConfig, options, cb);
});

cb

{function} cb

Optional callback function, called when all Shipit tasks are complete.

var gulp   = require('gulp');
var shipitCaptain = require('shipit-captain');

gulp.task('shipit', function(cb) {
  shipitCaptain(shipitConfig, cb);
});

License

MIT © Tim kelty