grunt-bower-install-simple
v1.2.8
Grunt Task for Installing Bower Dependencies
0/weekUpdated 3 years agoMITUnpacked: 24.0 KB
Published by Dr. Ralf S. Engelschall
npm install grunt-bower-install-simplegrunt-bower-install-simple
Grunt Task for Installing Bower Dependencies
> ATTENTION: Bower is deprecated and obsolete! Use this Grunt task only for legacy purposes, please!
Getting Started
This plugin requires Grunt ~0.4.0
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:
``shell`
npm install grunt-bower-install-simple --save-dev
Once the plugin has been installed, it may be enabled inside your
Gruntfile with this line of JavaScript:
`js`
grunt.loadNpmTasks("grunt-bower-install-simple");
Task Options
- color (default true): Whether output is colorized.bower --config.color=
The equivalent of .
- cwd (default process.cwd()): The directory from which Bower should run.
All relative paths in Bower will be calculated according to this.
The equivalent of bower --config.cwd=pwd .
- forceLatest (default false): Force latest dependency version on conflict.bower install --force-latest
The equivalent of .
- production (default false): Do not install project devDependencies.bower install --production
The equivalent of .
- interactive (default true): Makes Bower interactive, prompting whenever necessary.bower --config.interactive=true
The equivalent of .
- directory (default undefined): The path in which installed components should be saved.bower_components
This defaults to .bower --config.directory=
The equivalent of
.-
command (default install): Provide the bower command it should run.
Setting this to update will run bower update instead of bower install.Task Calling
_Run this task with the
grunt bower-install-simple command._Task targets, files and options may be specified according to the Grunt
Configuring tasks guide.
Usage Example
Assuming we have the following build environment:
-
Gruntfile.js:`js
// [...]
grunt.initConfig({
"bower-install-simple": {
options: {
color: true,
directory: "lib"
},
"prod": {
options: {
production: true
}
},
"dev": {
options: {
production: false
}
}
}
});
grunt.registerTask("bower-install", [ "bower-install-simple" ]);
// [...]
`-
:`json
{
"name": "sample",
"version": "0.0.0",
"devDependencies": {
"componentjs": "~1.2.7",
"jquery": "~2.1.4",
"lodash": "~3.10.1"
}
}
`Then running
is functionality-wise equivalent
to running bower --config.color=false --config.directory=lib install--production
. It will read the bower.json and install ComponentJS,
jQuery and Lo-Dash into the local lib` directory.