Building with Gulp


This article describes using the gulp-durandal plugin for building Durandal apps with Gulp.

Both scripts and views can be compiled into a single output file with this plugin. There is no double maintenance of path mapping required. The plugin allows various code layouts (bower, etc), using the paths already configured in your main.js file.

There's no need to be an expert with r.js's 60+ options. In many cases, the following should be enough:

gulp.task('durandal', function(){

Getting Started

Note: This plugin requires Gulp ~3.5.5.

If you haven't used Gulp before, be sure to check out the Getting Started guide, as it explains how to create a Gulpfile as well as install and use Gulp plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install gulp-durandal --save-dev

Once the plugin has been installed, it should be required inside your Gulpfile:

var durandal = require('gulp-durandal');

The "durandal" Stream

This plugin compiles all the scripts and views of a Durandal project into a single js file. The task expects that the Durandal files are under a single app dir (usually named _app) and that there is a single main module (usually at app/main.js) that contains both the requirejs path configuration and the initial module that executes.

While simple and minimalistic, this task can handle all known Durandal 2.x samples and starter kits (html, bower, node,, etc.) with almost no configuration.


In your project's Gulpfile, launch the plugin inside a task with the wanted configurations. The plugin will return the stream of the wanted file and it's source map.

var durandal = require('gulp-durandal');

gulp.task('durandal', function(){
            baseDir: 'app',   //same as default, so not really required.
            main: 'main.js',  //same as default, so not really required.
            output: 'main.js', //same as default, so not really required.
            almond: true,
            minify: true

For async tasks, handling of error and end events should be added.

gulp.task('durandal-async', function(cb){
        .on('error', cb)
        .on('end', cb);



Type: Boolean, Default value: false

Should the task emit information about it as it progresses.


Type: String, Default value: 'app'

The path, relative to the gulp cwd, to the root directory of your durandal app (usually called app or App in the durandal starter kits and generators).

This directory is expected to contain all your views, viewmodels, service modules etc. All files under it are are automatically included in the output: .js files as modules and text files (.html, *.json) as 'text!' prefixed modules.


Type: String, Default value: 'main.js'

The path to the main.js file of the application, relative to the baseDir.

This is where we expect to find the project's requirejs.config call which defines all the path mapping for the external modules and libraries.

This file also contains the main module of the application.

Note: The path and module configuration done in this file is extremely important for the build too. Promoting the 'Single Point of Truth` principle, we do not allow any configuration or path mapping outside of this file. We believe that if it is good enough for development, it is good enough for the build.


Type: String, Default value: path.basename(options.main)

Output js file's name.


Type: Boolean, Default value: false

Determines whether the output file is minified (using Uglify2).


Type: Boolean|String, Default value: false

True to wrap the generated code and include a Durandal specific version of AlmondJS, to replace the need for the much bigger requiresjs, and create a single and self sufficient output file. (Read more about AlmondJS and the Durandal version).

If the value is a string, it should be the path to an almond script, relative to the grunt cwd. The result is similar to setting the value to true, expect the almond script inserted is the one specified here and not the script that comes bundled with the task.


Type: String[], Default value: []

A list of extra modules to include in the output file, e.g. ['plugins/widget', 'plugins/dialog']. This can be used for all dynamically loaded modules that reside outside of the baseDir (such as Durandal's own plugins and transitions).

We will automatically include any module whose file is under the baseDir, as well as any of their explicit dependencies. Alas, non-explicit dependencies are not recognized automatically by r.js. If their files are outside the baseDir, they will not be recognized by our scanning process. Examples are the Durandal transitions that are loaded dynamically by convention, and Durandal plugins are loaded via app.configurePlugins({ widget: true }).

In short, all required modules must either reside under the baseDir, be an explicit dependency of a module under that dir, or be explicitly included via the extraModules option.

Module names are resolved and mapped to files according to the paths and mapping in the main config file, so use the same names as you would do in your code.


Type: Boolean, Default value: true

True to add default Durandal dynamic modules to options.extraModules. Adds all default Durandal plugins and transitions if the definition of plugins / transitions paths exists in the main config file.


Type: Boolean|String|String[], Default value: options.almond? true : false

Determines if a 'require([...])' call is to be inserted, and which modules are included in the list of required modules.

When options.almond is used, this value is true by default as almond requires usually to explicitly call require(['

']), which is not the convention for require js and Durandal.

The tasks avoids inserting the call if the value is set to false. If it true, it will insert the options.main module. If you need to explicitly specify the module names, use the string or string array value.


Type: Function, Default value: function(moduleName){return true;}

After all top level modules are resolved, they are passed via a filter function, so that you have a chance to exclude any modules for any reason you might have.

For example, if you would not like to include the views, you could supply the following function:

  return moduleName.indexOf('text!') == -1;

Note: This plugin is maintained by the community and is not part of the core Durandal project. More information can be found here.