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-heroku-branch

v1.0.0

Published

Wrapper to add the appropriate branches in git via grunt config

Downloads

8

Readme

grunt-heroku-branch

Wrapper to add the appropriate heroku remotes to git via grunt config

Getting Started

Prerequisite

You must install the Heroku toolbelt locally:

https://toolbelt.heroku.com/

This plugin requires Grunt ~0.4.5

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-heroku-branch --save-dev

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

grunt.loadNpmTasks('grunt-heroku-branch');

The "herokuBranch" task

Overview

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

grunt.initConfig({
  herokuBranch: {
    options: {
      changeCase: 'camelCase'
    },
    production: 'your-production-app-name',
    development: 'your-development-app-name',
  }
});

Options

options.changeCase

Type: String Default value: 'param' Valid values: 'sentenceCase'|'camelCase'|'pascalCase'|'snakeCase'|'paramCase'|'constantCase'

How to convert the build target to a remote name. This option is directly passed to https://www.npmjs.com/package/change-case

Example:

grunt.initConfig({
  herokuBranch: {
    options: {
      changeCase: 'camelCase'
    },
    remote_one: 'your-production-app-name',
    remoteTwo: 'your-development-app-name',
  }
});

Would produce the following result for git remote -v:

remoteOne	[email protected]:your-development-app-name.git (fetch)
remoteTwo	[email protected]:your-development-app-name.git (push)

Usage Examples

Default Options

grunt.initConfig({
  herokuBranch: {
    production: 'your-production-app-name',
    development: 'your-development-app-name',
  }
});

Would produce the following result for git remote -v:

production	https://git.heroku.com:your-development-app-name.git (fetch)
development	https://git.heroku.com:your-development-app-name.git (push)

Custom Options

Customize the case used;

grunt.initConfig({
  options: {
    changeCase: 'constantCase'
  },
  target1: {
    name: 'production',
    url: 'your-production-app-name'
  },
  target2: {
    name: 'development',
    url: 'your-development-app-name'
  }
});

Running grunt herokuBranch:target1 and grunt herokuBranch:target2 will produce the following results for git remote -v:

PRODUCTION	https://git.heroku.com:your-production-app-name.git (fetch)
PRODUCTION	https://git.heroku.com:your-production-app-name.git (push)
DEVELOPMENT	https://git.heroku.com:your-development-app-name.git (fetch)
DEVELOPMENT	https://git.heroku.com:your-development-app-name.git (push)

Contributing

JSHint and JSBeautifier steps should pass.

Release History

0.2.2

Stable version with test coverage and docs.