node package manager



Build everything with right tool

Richard Buckminster "Bucky" Fuller was an American systems theorist, architect, engineer, author, designer, inventor, and futurist


npm install fuller -g


fuller [-w] [-z] [-v] [--src] [--dst] [--taskName]
--watch, -w     Watch source directory for changes
--src           Relative path to directory with source files
--dst           Relative path to directory for compiled files
--dev, -z       Developer mode (usually this means no minifing and compressions, but depends from plugin)
--verbose, -v   Verbose mode
--taskName      Run task from plan


Plan is a description file which contains Fuller declarative config (plan.js by default):

plan = {
    "task:default": {
        "beltname": beltTasks
    "belt:beltname": {
        toolname: {
            toolname: {...}


Belt represents a chain of tools. Take a look at belt definition example:

"belt:js": {
    options: {
        src: "js",
        dst: "js"
    "concat": {
        "common-js": {
            "uglify": {}

Belt definition starts with "belt" keyword and ends with belt name - belt:name - in the given example belt is created with js name. options is reserved property name - it may contain options that extend default plan's one - in out case default plan source and destination folders' paths are concatenated with belt's - files will be read from 'source/js/' folder and written to 'destination/js/' folder. Other properties for belt object represent Fuller tools. Here we chain concat, common-js and uglify plugins.


Tool is a plugin that does something with provided data. In belt tools may be run in chain and next tool will receive result of previous one's work or they can work parallel. Tool looks like this:

    options,    // optional 

Options may contain described above information or any additional settings supported by tool.


Task definition starts with "belt" keyword. Task is a declarative description of what should be done. Task may be function or an object or anythings - check the tool docs for details on task look.

If no task was specified on Fuller run default one will be used.


You can specify default options in global section, or in tool's part of the plan. Options declared in tools extend root options, source and destination paths are concatenated.

Don't forget about verbose mode here if you need it.

The fuller var in your task function is a pointer to global fuller object.

Bonus, you can specify dev task. It'll be run before all others tasks when you'll use -z(--dev) option.