Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A simple build tool for html/js/css projects.
JavaScript HTML

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
bin
lib
test
.gitignore
.npmignore
.travis.yml
CHANGELOG.md
README.md
index.js
package.json

README.md

Build Status

buddy(1)

buddy(1) is a build tool for js/css/html projects. It helps you manage third-party dependencies, compiles source code from higher order js/css/html languages (CoffeeScript/LiveScript/Handlebars/Stylus/Less/Jade), automatically wraps js files in module definitions, statically resolves module dependencies, and concatenates (and optionally compresses) all souces into a single file for more efficient delivery to the browser.

Current version: 0.10.0 [See Change Log for more details]

Features

  • Allows you to write js modules without the module boilerplate (similar to Node.js)
  • Resolves js module dependencies automatically
  • Supports efficient lazy runtime evaluation by storing js modules as strings
  • Compiles CoffeeScript, LiveScript, Handlebars, Stylus, Less, and Jade source files
  • Concatenates js modules into a single file
  • Runs js and css code through linters to check for syntax errors
  • Watches for source changes and builds automatically
  • Serves static files from specified directory on specified port
  • Refreshes connected browsers after each change
  • Inlines css @imports automatically
  • Supports execution of a test script after each build
  • Copies libraries from GitHub to your project
  • Copies assets from a local destination to your project

Installation

To avoid running buddy(1) directly as a global command, and thus avoid versioning problems across different projects, it is highly recommended that you instead install the separate buddy-cli command line interface system-wide:

$ npm -g install buddy-cli

...then create a package.json file for each project, locally installing buddy as a devDependency:

{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  }
}
$ cd path/to/project
$ npm install

Usage

Usage: buddy [options] <command> [path/to/package.json or path/to/buddy.js or path/to/buddy.json]>

Commands:

  install [config]       install dependencies
  build [config]         build js and css sources
  watch [config]         watch js and css source files and build changes
  deploy [config]        build compressed js and css sources
  ls                     list all previously created files and directories
  clean                  remove all previously created files and directories

Options:

  -h, --help      output usage information
  -V, --version   output the version number
  -c, --compress  compress output for production deployment
  -l, --lint      check output for syntax and logic errors
  -r, --reload    reload all connected live-reload clients on file change during watch
  -s, --serve     create a webserver to serve static files during watch
  -t, --test      run test command on build completion
  -L, --lazy      convert js modules for lazy evaluation
  -v, --verbose   print all messages for debugging

Examples

Generate www/main.js by concatenating and modularizing all dependencies in src or libs/js referenced in src/main.js:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "dependencies": {
    "simple-browser-require": "*"
  },
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "build": {
      "js": {
        "sources": ["src", "libs/js"],
        "targets": [
          {
            "input": "src/main.js",
            "output": "www/main.js"
          }
        ]
      }
    }
  }
}
$ buddy build

Generate www/main.js with references to dependencies installed via npm:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "dependencies": {
    "simple-browser-require": "*"
    "underscore": "1.4.4"
  },
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "build": {
      "js": {
        "sources": ["src"],
        "targets": [
          {
            "input": "src/main.js",
            "output": "www/main.js"
          }
        ]
      }
    }
  }
}
$ buddy build

First compile all CoffeeScript files in libs/src/coffee, then generate www/main.js by concatenating and modularizing all dependencies referenced in 'src/main.js':

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "dependencies": {
    "simple-browser-require": "*"
  },
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "build": {
      "js": {
        "sources": ["src", "libs/js", "libs/src/coffee"],
        "targets": [
          {
            "input": "libs/src/coffee",
            "output": "libs/js"
          },
          {
            "input": "src/main.js",
            "output": "www/main.js"
          }
        ]
      }
    }
  }
}
$ buddy build

Generate www/main.js and an additional widget www/widget.js using shared sources (avoid duplicating dependencies):

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "dependencies": {
    "simple-browser-require": "*"
  },
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "build": {
      "js": {
        "sources": ["src", "libs/js"],
        "targets": [
          {
            "input": "src/main.js",
            "output": "www/main.js",
            "targets": [
              {
                "input": "src/widget.js",
                "output": "www/widget.js"
              }
            ]
          }
        ]
      }
    }
  }
}
$ buddy build

Compile a CoffeeScript project for Node.js, skipping module wrapping and concatenation:

package.json
{
  "name": "myproject",
  "description": "This is my server project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "build": {
      "js": {
        "sources": ["src/coffee"],
        "targets": [
          {
            "input": "src/coffee",
            "output": "js",
            "modular": false
          }
        ]
      }
    }
  }
}
$ buddy build

Copy project boilerplate from a local directory into the project root:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "dependencies": {
      ".": {
        "sources": ["../../boilerplate/project"]
      }
    }
  }
$ buddy install

Download js dependencies browser-require and jQuery, then concatenate and compress to www/libs.js for inclusion in html:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "dependencies": {
      "libs/vendor": {
        "sources": [
          "popeindustries/browser-require",
          "jquery@1.9.1"
        ],
        "output": "www/libs.js"
      }
    }
  }
$ buddy install

Download visionmedia/nib Stylus sources, specifying a specific directory to be referenced in your builds:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "dependencies": {
      "libs/src/css": {
        "sources": [
          "visionmedia/nib#lib/nib"
        ]
      }
    }
  }
}
$ buddy install

Start a basic web server and refresh the browser (using the Live-Reload browser plugin) after each build triggered by source file changes:

package.json
{
  "name": "myproject",
  "description": "This is my web project",
  "version": "0.1.0",
  "devDependencies": {
    "buddy": "0.10.0"
  },
  "buddy": {
    "settings": {
      "server": {
        "directory": "www",
        "port": 8080
      }
    }
  }
}
$ buddy watch -rs

Configuration

Complete annotated buddy.js configuration file:

// Project build configuration.
exports.build = {
  js: {
    // Directories containing potential js source files for this project ('node_modules' are added by default).
    sources: ['a/coffeescript/source/directory', 'a/js/source/directory'],
    // One or more js build targets.
    targets: [
      {
        // An entrypoint js (or equivalent) file to be wrapped in a module definition,
        // concatenated with all it's resolved dependencies.
        input: 'a/coffeescript/or/js/file',
        // A destination in which to save the processed input.
        // If a directory is specified, the input file name will be used.
        output: 'a/js/file/or/directory',
        // An alternate destination in which to save the compressed output.
        output_compressed: 'a/js/file/or/directory',
        // Targets can have children.
        // Any sources included in the parent target will NOT be included in the child.
        targets: [
          {
            input: 'a/coffeescript/or/js/file',
            output: 'a/js/file/or/directory'
          }
        ]
      },
      {
        // Files are batch processed when a directory is used as input.
        input: 'a/coffeescript/or/js/directory',
        output: 'a/js/directory',
        // Skips module wrapping (ex: for use in server environments).
        modular: false
      }
    ]
  },
  css: {
    // Directories containing potential css source files for this project.
    sources: ['a/stylus/directory', 'a/less/directory', 'a/css/directory'],
    // One or more css build targets
    targets: [
      {
        // An entrypoint css (or equivalent) file to be processed,
        // concatenated with all it's resolved dependencies.
        input: 'a/stylus/less/or/css/file',
        // A destination in which to save the processed input.
        // If a directory is specified, the input file name will be used.
        output: 'a/css/file/or/directory'
      },
      {
        // Files are batch processed when a directory is used as input,
        // though @import'ed dependencies are still resolved and inlined.
        input: 'a/stylus/less/or/css/directory',
        output: 'a/css/directory'
      }
    ]
  }
}

// Project dependency configuration.
exports.dependencies = {
  // A destination directory in which to place third-party library dependencies.
  'a/vendor/directory': {
    // An ordered list of dependencies
    sources: [
      // A github user/repo.
      // Install the 'browser-require' source when using Node-style modules.
      'popeindustries/browser-require',
      // A named library with or without version (ex: jquery@latest, backbone, backbone@1.0.0).
      // Version identifiers follow the npm semantic versioning rules.
      'library@version'
    ],
    // Dependencies can be packaged and minified to a destination file
    output: 'a/js/file'
  },
  // A destination directory in which to place source library dependencies.
  'a/source/directory': {
    sources: [
      // A github user/repo.
      // Will use the 'main' properties of
      // components.json or package.json to identify the file to install.
      'username/repo',
      // A github user/repo with specific file or directory locations.
      'username/repo#a/file/or/directory|another/file/or/directory',
      // A local file or directory to copy and install.
      '../a/file/or/directory'
    ]
  }
}

// Project settings configuration.
exports.settings = {
  // Run a command after build
  test: 'command --flags',
  // Configure webserver
  server: {
    // Defaults to project root
    directory: 'a/project/directory',
    // Defaults to 8080
    port: 8000
  }
}

Concepts

BUILD

Project Root: The directory from which all paths resolve to. Determined by location of the configuration file.

Sources: An array of directories from which all referenced files are retrieved from. Note: A js module's id is derived from it's relative path to it's source directory.

Targets: Objects that specify the input and output files or directories for each build. Targets are built in sequence, allowing builds to be chained together. Note: A js target can also have nested child targets, ensuring that dependencies are not duplicated across related builds.

Target parameters:

  • input: file or directory to build. If js (or equivalent) file, all dependencies referenced will be concatenated together for output. If directory, all compileable files will be compiled, wrapped in module definitions (js), and output to individual js/css files.

  • output: file or directory to output to.

  • targets: a nested target that prevents the duplication of source code with it's parent target.

  • modular: a flag to prevent js files from being wrapped with a module definition.

  • output_compressed: an alternate file or directory to use for compressed output.

MODULES

Each js file is wrapped in a module declaration based on the file's location. Dependencies are determined by the use of require() statements:

var lib = require('./my/lib'); // in current package
var SomeClass = require('../someclass'); // in parent package
var util = require('utils/util'); // from root package

lib.doSomething();
var something = new SomeClass();
util.log('hey');

Specifying a module's public behaviour is achieved by decorating an exports object:

var myModuleVar = 'my module';

exports.myModuleMethod = function() {
  return myModuleVar;
};

...or overwriting the exports object completely:

function MyModule() {
  this.myVar = 'my instance var';
};

MyModule.prototype.myMethod = function() {
  return this.myVar;
};

module.exports = MyModule;

Each module is provided with a module, exports, and require reference.

When require()-ing a module, keep in mind that the module id is resolved based on the following rules:

  • packages begin at the root folder specified in build > js > sources:
'Users/alex/project/src/package/main.js' > 'package/main'
  • uppercase filenames are converted to lowercase module ids:
'my/package/Class.js' > 'my/package/class'

See node.js modules for more info on modules.

NOTE: require boilerplate needs to be included in the browser to enable module loading. It's recommended to install a library like popeindustries/browser-require (npm: simple-browser-require).

DEPENDENCIES

Dependency resources are installed from local locations or remotely from Github.

Sources: An array of local or remote resource locations.

  • destination: each group of sources will be installed to the project relative location specified.

  • identifier: github username/repo identifiers are preferred, but it is also possible to use identifiers from the bower package manager: 'jquery', 'backbone', 'underscore', etc.

  • versioning: github sources can specify a version by appending @ and a npm-style symantic version: '*', '1.2.3', '1.x', '~1.2.0', '>=1.2.3'

  • resources: specific resources can be specified by appending # and a list of | separated relative file or directory locations: 'username/repo#a/file/or/directory|another/file/or/directory'

Output: A file destination to concatenate and compress the source contents. The order of sources determines the content order.

License

(The MIT License)

Copyright (c) 2011 Pope-Industries <alex@pope-industries.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Something went wrong with that request. Please try again.