Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

saucer - coffeescript boilerplate


Saucer is an opinionated template project for coffee/javascript development. It gets you up and running with the following tools:

and the frontend libs:

(if you don't need any of these, you can just delete them).


clone the source

git clone my-project
cd my-project

install dependencies

setup google closure

Move (or create a symlink to) the closure compiler jar to lib/closure/compiler.jar. For example, in osx:

% mv ~/Downloads/compiler-latest/compiler.jar lib/closure/.


% ln -s /usr/local/Cellar/closure-compiler/20120917/libexec/build/compiler.jar lib/closure/.

Initialize google closure-tools submodule:

% git submodule init
% git submodule update

install node modules

% npm install

source tree

Saucer organizes the code thus:

├── - the grunt task file
├──        - this file
├── build            - the build directory, for compiled code
├── coffee           - coffeescript code
│   ├── src          - coffeescript source files
│   └── test         - coffeescript test files
├── js               - javascript code (generated from coffee/)
│   ├── deps.js      - generated dependencies file (closure)
│   ├── src          - javascript source files
│   └── test         - javascript test files
├── lib              - libraries
│   ├── bootstrap    - bootstrap js/css library
│   └── closure      - closure library + compiler
├── node_modules     - npm installed modules
└── package.json     - package info

grunt tasks

Available tasks (ignore others):

    coffee  Compile CoffeeScript files (coffee/ to js/)
      deps  Generates file dependencies (js/deps.js)
      test  Runs jasmine tests in the commandline.
testserver  Runs jasmine tests in a webserver.
   compile  Closure compiles the source (js/src/).
   default  Alias for "compile" task.
     watch  Watches coffee/ and re-runs "deps"
     clean  Clear files and folders (js/, build/)

Common workflow:

  • write code in coffee/src/
  • write corresponding tests in coffee/test/
  • test with grunt --config test
  • test with grunt --config testserver
  • compile code with grunt --config compile


writing specs

Write your jasmine specs in the test part of the source tree. Your test directory should mirror your src directory, with every filename.{coffee,js} having a corresponding filename.spec.{coffee,js}. This one-to-one test to src correspondence:

  • makes sure you do write a test file for every src file.
  • easily identifies and properly scopes spec files, for simpler debugging.

For example, in coffeescript:

├── src
│   ├──
│   └──
└── test

And in javascript:

├── deps.js
├── src
│   ├── hello.js
│   └── main.js
└── test
    ├── hello.spec.js
    └── main.spec.js

running from the command line

You can run the tests from the commandline (using phantomjs):

grunt --config test


running with a webserver

You can run the tests from the commandline (using phantomjs):

grunt --config testserver




coffeescript boilerplate



No releases published


No packages published
You can’t perform that action at this time.