Remove documentation about Bower dependencies
We are now using yarn (npm).
This commit is contained in:
parent
e167958135
commit
c754722867
1 changed files with 0 additions and 32 deletions
|
@ -258,37 +258,5 @@ yarn build-release
|
|||
|
||||
Then, run the tests using `grunt test-release:osx --dir=release`, replacing `osx` with `linux` or `win` depending on your platform.
|
||||
|
||||
## Dependencies
|
||||
|
||||
**Note**: You probably won't end up doing this. Feel free to skip for now.
|
||||
|
||||
Dependencies are managed by [bower](http://bower.io) and built with
|
||||
[grunt](http://gruntjs.com). To change them, you'll need to install node and
|
||||
npm, then run `npm install` to install bower, grunt, and related plugins.
|
||||
|
||||
### Adding a bower component
|
||||
|
||||
Add the package name and version to bower.json under 'dependencies' or `bower install package-name --save`
|
||||
|
||||
Next update the "preen" config in bower.json with the list of files we will
|
||||
actually use from the new package, e.g.:
|
||||
|
||||
```
|
||||
"preen": {
|
||||
"package-name": [
|
||||
"path/to/main.js",
|
||||
"directory/**/*.js"
|
||||
],
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
If you'd like to add the new dependency to js/components.js to be included on
|
||||
all html pages, simply append the package name to the concat.app list in
|
||||
`bower.json`. Take care to insert it in the order you would like it
|
||||
concatenated.
|
||||
|
||||
Now, run `grunt` to delete unused package files and build `js/components.js`.
|
||||
|
||||
Finally, stage and commit changes to bower.json, `js/components.js`,
|
||||
and `components/`. The latter should be limited to files we actually use.
|
||||
|
|
Loading…
Reference in a new issue