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

v0.2.0

Published

A grunt task that makes working with release branches (aka gh-pages) a breeze"

Downloads

4

Readme

grunt-release-branch

A grunt task that makes working with release branches (aka gh-pages) a breeze

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

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

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

What is the problem with release branches aka gh-pages branches?

When developing for the web, we usually have bunch of build steps which take care of concatenation, minification, inlining templates, generating html snapshots and so on and so on...

After running through all those steps, the final output is usually placed into an output directory that is not commited into version control. Following the release branch pattern we take this output and place it on an orphan branch, were some other mechanism can kick in and e.g. publish it as a website. That's exactly how it works with github as well.

This grunt plugin consits of two tasks to assist you for those scenarios.

releaseBranchPre task

This task should be run before all other build steps. It simply does git branch -D gh-pages and git checkout -b gh-pages under the covers. Please note that the branch name can be configured with the releaseBranch option.

releaseBranch task

This task should run as the last command in your build orchestration. It erases everything it moves all the files from your output directory to the root level of your working directory while deleting all other stuff except your .git folder. It than optionally commits and pushs using the --force parameter.

configuring the htmlSnapshot task



    var releaseBranchOptions = app: {
                                        options: {
                                            //the name of the orphan branch. Default is gh-pages
                                            releaseBranch: 'gh-pages',
                                            //the name of the remote repository. Default is origin
                                            remoteRepository: 'origin',
                                            //the name of the output directory. Default is dist
                                            distDir: 'dist',
                                            //the commit message to be used for the optional commit
                                            commitMessage: 'RELEASE',
                                            //should files be automatically commited on the orphan branch
                                            commit: true
                                            //should the orphan branch be pushed to the remote repository
                                            //default is false
                                            push: true
                                            //a blacklist of things to keep on the root level. By default only
                                            //the .git folder will be kept.
                                            blacklist: [
                                                '.git'
                                            ]
                                        }
                                    };


    grunt.initConfig({
        releaseBranchPre: releaseBranchOptions,
        releaseBranch: releaseBranchOptions
    });

Release History

  • 0.1.0 - Initial release