Use Stitch to package up your modules for use with Rendr (github.com/airbnb/rendr).
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-rendr-stitch --save-dev
The "rendr_stitch" task
In your project's Gruntfile, add a section named
rendr_stitch to the data object passed into
In this example, you can see how to use
We can then use Stitch in the browser to require any of the source files.
var UserShowView = ;
Aliases allow us to use the the same paths for requiring NPM modules in both Node.js and in the browser. For example:
var BaseView = ;
In Node.js, this path will tell the module loader to look into the NPM module named
rendr to find the specified module. In the browser, we can do the same thing because we've bundled
node_modules/rendr/shared/**/*.coffee and set up an alias to
An array of file glob patterns to pass as dependencies to
Aliases provide a way to do fancy bundling of Stitch packages in order to replicate something like NPM module paths from Node. Each element in the array is an object with
to properties. For example:
dependencies:from: 'some/path/on/disk' to: 'fancy/path/in/client'
some/path/on/disk directory looks like this:
|- util.js |- lib/something.js
Then, in the client-side you can require the module using the aliased path:
var something = ;
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
Better support for multi tasks.
npmDependencies for more flexibility.
npmDependencies option for packaging NPM modules for browser.
stitch dependency for fork that supports Windows file paths.
tmp dir on every run, to prevent picking up old files.