forked from bobundov/bower-installer
-
Notifications
You must be signed in to change notification settings - Fork 5
/
Copy pathpackage.json
54 lines (54 loc) · 4.79 KB
/
package.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
{
"name": "bower-installer",
"version": "0.8.4",
"preferGlobal": "true",
"description": "Tool for installing bower dependencies that won't include entire repos",
"main": "bower-installer.js",
"dependencies": {
"node-fs": "~0.1.7",
"bower": "~1.3.8",
"colors": "~0.6.0-1",
"lodash": "~0.9.1",
"glob": "~3.2.7",
"nopt": "~2.1.2",
"async": "~0.2.9",
"mkdirp": "~0.3.5"
},
"engines" : { "node" : ">=0.10.0" },
"devDependencies": {
"grunt": "~0.4.2",
"grunt-jasmine-node": "0.2.1",
"async": "~0.2.9",
"rimraf": "~2.2.2"
},
"scripts": {
"test": "grunt"
},
"repository": {
"type": "git",
"url": "https://github.com/blittle/bower-installer"
},
"keywords": [
"bower",
"install",
"dependencies"
],
"author": {
"name": "Bret Little"
},
"license": "BSD",
"bin": {
"bower-installer": "./bower-installer.js"
},
"readme": "bower-installer\n===============\n\nTool for installing bower dependencies that won't include entire repos. Although Bower works great\nas a light-weight tool to quickly install browser dependencies, it currently does not provide much\nfunctionality for installing specific \"built\" components for the client.\n\n#Bower installs entire repositories\n\n```javascript\n{\n \"name\" : \"test\",\n \"version\": \"0.1\",\n \"dependencies\" : {\n \"backbone\" : \"latest\"\n }\n}\n```\nIf `bower install` is run on this configuration file, the entire backbone repository will be pulled down\nand copied into a components directory. This repository is quite large, when probably only a built js and css\nfile are needed. Bower conveniently provides the `bower list --paths` command to list the actual main files associated\nwith the components (if the component doesn't define a main, then the whole repository is listed instead).\n\n#Bower Installer\nBower installer provides an easy way for the main files to be installed or moved to one or more locations. Simply add to\nyour bower.json an `install` key and `path` attribute:\n\n```javascript\n{\n \"name\" : \"test\",\n \"version\": \"0.1\",\n \"dependencies\" : {\n \"backbone\" : \"latest\"\n },\n \"install\" : {\n \"path\" : \"some/path\"\n }\n}\n```\n\nInstall bower-installer by executing\n\n```bash\nnpm install -g bower-installer\n```\n\nFrom the terminal in the same directory as your bower.json file, enter:\n```bash\nbower-installer\n```\n\nAfter executing this, `backbone.js` will exist under `some/path` relative to the location of your\nbower.json file.\n\n#Overriding main files\nA lot of registered components for bower do not include bower.json configuration. Therefore, bower does not know\nabout any \"main files\" and therefore, by default bower-installer doesn't know about them either. Bower-installer\ncan override an existing main file path or provide a non-existant one:\n\n```javascript\n{\n \"name\" : \"test\",\n \"version\": \"0.1\",\n \"dependencies\" : {\n \"backbone\" : \"latest\",\n \"requirejs\" : \"latest\"\n },\n \"install\" : {\n \"path\" : \"some/path\",\n \"sources\" : {\n \"requirejs\" : \"components/requirejs/require.js\"\n }\n }\n}\n```\nIf bower installer is run on this configuration, `require.js` and `backbone.js` will all appear under\n`some/path` relative to your bower.json file.\n\n#Install multiple main files\nFor one reason or another you may want to install multiple files from a single component. You can do this by providing\nan `Array` instead of a `String` inside the sources hash:\n\n```javascript\n{\n \"name\" : \"test\",\n \"version\": \"0.1\",\n \"dependencies\" : {\n \"jquery-ui\" : \"latest\"\n },\n \"install\" : {\n \"path\" : \"some/path\",\n \"sources\" : {\n \"jquery-ui\" : [\n \"components/jquery-ui/ui/jquery-ui.custom.js\",\n \"components/jquery-ui/themes/start/jquery-ui.css\"\n ]\n }\n }\n}\n```\n\n#Install files to multiple locations\nFiles can be installed to multiple locations based upon file type. Do so by modifying the `path` to be a map of file-type\n locations. Example:\n ```javascript\n{\n \"name\" : \"test\",\n \"version\": \"0.1\",\n \"dependencies\" : {\n \"jquery-ui\" : \"latest\"\n },\n \"install\" : {\n \"path\" : {\n \"css\": \"src/css\",\n \"js\": \"src/js\"\n },\n \"sources\" : {\n \"jquery-ui\" : [\n \"components/jquery-ui/ui/jquery-ui.custom.js\",\n \"components/jquery-ui/themes/start/jquery-ui.css\"\n ]\n }\n }\n}\n```\n",
"readmeFilename": "README.md",
"bugs": {
"url": "https://github.com/blittle/bower-installer/issues"
},
"_id": "[email protected]",
"dist": {
"shasum": "37c85aed13e693f4d1347cf7dae5e9d68a40a28e"
},
"_from": "bower-installer@",
"_resolved": "https://registry.npmjs.org/bower-installer/-/bower-installer-0.3.0.tgz"
}