node package manager
It’s your turn. Help us improve JavaScript. Take the 2017 JavaScript Ecosystem Survey »



A Node.js build tool to gather/order/filter/mignify all your JS files and their dependencies. Greatly inspired from Apache Ant.

We used this tool in KadOH :

  • to gather : KadOH is composed of many small JS files spread among different directories that should be gather in a single file.
  • to order : KadOH has a dependency tree : each file depends on other ones that should be included and placed before in the build, and so on.
  • to filter : we have different build dependending on the configuration (should run in Node.js or in browser, should use this transport type or an other..) : some files should be excluded from the build in some case.
  • to mignify : smaller is often better : UglifyJS.

Q : In browser environement, this could be seen as an alternative to AMD loaders ?

Yes and no, the 2 approachs could and should live together. AMD is used to load modules and submodules that best fit the needs of the client browser avoiding the load of useless code. Nethertheless, some modules or submodules depends on other ones independently from the client browser configuration. If you have these useful dependencies gathered in one single file, you will probably spare multiple tiring asynchronous loads.

If you are asking this question, you should probably have a look to ender.


I'm on npm girls !

$ npm install jsCicada

See it in action

You can find an example of use in the sandbox directory : execute the tes-script.js..

$ cd sandbox/
$ node test-script.js

..and see what happened according to the build.json.

But you should also have a look at KadOH.


Add build.json...

Include a valid build.json file in the root directory of your project to configure your builds.

Example :

  "basedir"     : ".",            // base directory
  "directories" : {       // directory name shortcuts
    "src"     : "src",
    "dist"    : "dist",
    "jquery"  : "src/ext/jquery"
  "targets" : {         // different build configurations are called "targets"
    "normal" : {       // "normal" is the name of a target
      "entry"   : "[src]/node",   // entry point of your build : where to start finding dependencies
      "build"   : "[dist]/project.js", //where you want to place the build file
      "exclude" : [
      "[src]/notThat"  //simply exclude it from the build
    "normal-mini" : {
      "depends" : "normal", //that means the build "normal-mini" have the same configuration as "normal" plus the ones that you specify/override
      "mignify" : true, //do you want me to mignify your build ?
      "build"   : "[dist]/project.min.js"
    "no-jquery" : {
      "depends" : "normal",
      "exclude" : [
        "[jquery]/*" //you don't want all the jquery stuff..
      "build"   : "[dist]/project-nojquery.js"

... add dependencies...

In any of your JS file indicate in the header (or anywhere else) to jsCicada which files you want to see included before this one in the build :

Example :

 * Dep : [src]/other/usefull.js
 * Dep : [jquery]/jquery.js
// your awsome code goes here : 
var big = "bang";

Note : you can ommit the extension (.js) that will be added afterwards.

2nd note : is it usefull to specify that when you add the same file as dependency several times (in different files), it will be included only once and at the right position ?

...and build !

builder = require('jsCicada').builder;
var b = new builder(); //look for build.json in the working directory 
var b = new builder('path/to/build.json');
var b = new builder({my_build_configuration : 'goes here'});
//or['target_name', 'target_bis_name']);

That's it.


Authors :

Dependencies :


  • documentation
  • build configuration : keywords based conditions for inclusion/exculsion of files
  • avoid useless mignify : try to find '.min.js' before.
  • add a binary