github.com/joey-fossa/fossa-cli@v0.7.34-0.20190708193710-569f1e8679f0/docs/integrations/bower.md (about) 1 # Bower 2 3 ## Installation 4 5 Bower support in FOSSA CLI depends on the following tools existing in your environment: 6 7 - Node.js (defaults to `node`, configure with `$NODE_BINARY`) 8 - Bower (defaults to `bower`, configure with `$BOWER_BINARY`) 9 10 ## Configuration 11 12 Automatic: Run `fossa init` to detect all directories with a `bower.json` file at their roots and create a module for each. 13 14 Manual: Add a module with `type` set to `bower`, `dir` set to the directory where `bower.json` was found, and `target` . 15 16 ```yaml 17 analyze: 18 modules: 19 - name: your-bower-project 20 type: bower 21 path: bower.json 22 target: configuration/bower.json 23 ``` 24 25 ## Analysis 26 27 fossa runs `bower list --json` and parses the output to create a dependency tree. 28 29 ## Known limitations 30 31 - We assume that your Bower packages are installed at `bower_components`. Ideally, we would read this location from your `bower.json`, but this has not yet been implemented. 32 - We assume that you have installed exactly one version of each of your transitive Bower dependencies. If you have manually edited your local Bower build process, this may not be true. That said, having multiple versions of a Bower dependency is generally indicative of a broken build.