Automagically wire-up installed Bower components into your RequireJS config
Automagically wire-up installed Bower components into your RequireJS config, with the ability to alias and prefix module IDs.
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, install this plugin with this command:
npm install grunt-bower-requirejs-alias --save-dev
bower task is run it merges the paths of installed Bower components into the
paths property of your RequireJS config.
You trigger this task from another task in your Gruntfile or through the CLI:
Specify a relative path to your RequireJS config.
Make sure to specify the
baseUrl property in your RequireJS config if you want to use relative paths.
Specify components to be excluded from being added to the RequireJS config.
Generate paths relative to a specific directory. This option is for anyone not using
data-main who wishes to set their own base.
Prefix all bower module ids with a specific string
Alias one module name to another. Applied before prefix.
You need to already have a config.js file at the location specified by
rjsConfig. At a minimum, the file should look like this:
You still need to create a path for your js files. The grunt task will only create paths for third party libraries specified in
The task does not overwrite the config file, it just adds additional paths to it. So paths you add will be preserved. Keep in mind that if you change or remove one of your bower dependencies after you've run the task, that path will still exist in the config file and you'll need to manually remove it.
Although RequireJS does not provide a
bower.json file, a path to
require.js will still be created in your
rjsConfig file. The path's name will be
requirejs. If you are optimizing your scripts with
r.js you can use this path to make sure RequireJS is included in your bundle.
BSD license and copyright Google