If you - like me, like to use Browserify to speedup the process of developing your web applications, you will very soon feel the need of any sort of automated tasks that can lead you to a more continuous development ecosystem. Let’s begin.

Why Browserify?

Because you need that important step before your code gets bundled and deployed. Browserify lets you write code for the browser in the same way you would write it in Node.js. Every time you like to use a NPM package you would do a simple npm install awesome_package followed by a var awesome = require('awesome_package'). Good news is that you can now agnostically use require() inside your code for the client using Browserify. It will take care of bundling all your files, handle dependency injections and file caching.

You can also create your own custom modules that you will require() in the same way as you would do with a package. When you load a module, make sure you start the path by either a ../ or ./ (without adding the .js extension). require('data/module1.js'); is wrong, as it will not be resolved relatively, but rather as a NPM package named data from your node_modules directory. The way to do it is require('./data/module');

When Grunt comes to the rescue

As more and more of my peers say “Hello Gulp, it’s nice to meet you!”, we will still use Grunt for the time being. Grunt is a task runner that effortlessly lets you automate your pain in the _ss jobs. Before you continue make sure you read this page gruntjs.com/getting-started, where you will learn how to install the command line interface, create a Gruntfile.js and add a simple gruntplugin.

Where are my gruntplugins?

Gruntplugins are half community half official NPM packages that take care of the most common tasks such as: minification, compilation, unit testing, linting, etc. Official maintained packages have the word contrib in their name.

In a clean development environment we need at least: Browserify to watch for file changes, bundle all into one big JS file and run a live reloading server. To do that we need to install the followings:

npm install grunt-browserify grunt-contrib-connect grunt-contrib-watch connect-livereload --save-dev


This will be the file that will contain all our tasks:

module.exports = function (grunt) {
    browserify: {
      dev: {
        src: 'src/js/main.js',
        dest: 'dist/js/main.bundle.js',
        options: {
          browserifyOptions: {
            debug: true
    watch: {
      dev: {
        files: ['src/js/**/*.js', 'dist/*.html'],
        tasks: ['browserify'],
        options: {
          livereload: true
    connect: {
      dev: {
        options: {
          port: 8080,
          base: './dist',
          middleware: function (connect, options, middlewares) {
            return middlewares;


  grunt.registerTask('serve', ['browserify:dev', 'connect:dev', 'watch:dev']);

grunt.loadNpmTasks() loads the above installed gruntplugins and grunt.registerTask() creates our main task (giving it the alias serve). You can even pass parameters to the indivitual tasks (like in our case dev). Imagine you would have multiple configuration in your Gruntfile.js for production and development environments; where in production you would set the browserifyOptions { debug: false } for exemple.

debug creates the sourcemap for your bundled.js file. Also if for exemple, you will ever use transforms with your bundle, you can add them like this: transform: ['hbsfy'] in your browserifyOptions {} object.

connect task uses the connect-livereload package to start a mirrored server on a different port and watch for file changes. Your HTTP server will have it’s root in the dist/ folder.

We are finally ready to run our Gruntfile main task, serve. Go to your terminal and type grunt serve. Your web application is currently running port 8080, files were just being bundled and are currently watched for updates. Live reload acts as a middleware and the browser will automagically reload with the new files.

To conclude

As a very proud Meteor developer, I find this kind of development process very challenging and time consuming; but once you get pass the boilerplate phase, Grunt can be a lot of fun. I personally like the amount of debug information Grunt tasks give you, compared to Meteor. Even if the latter has everything of the above amazingly packed inside the box, it’s often complicated to trace bugs in Meteor if you were to read the terminal outputs only.

Long live well-written NPM packages!