setup.sh - Adapt to local version of composer/bower/karma
authorTim Otten <totten@civicrm.org>
Sat, 3 Jan 2015 21:24:04 +0000 (13:24 -0800)
committerTim Otten <totten@civicrm.org>
Sat, 3 Jan 2015 21:24:04 +0000 (13:24 -0800)
commit77665792d704adaa68dbbb3d7df93321b74d5add
treebaa8df710ffcbfa04f2d8eb69ac6f64cb7be4f54
parent1b0867663b700ad394a37383c6125ae9fde41570
setup.sh - Adapt to local version of composer/bower/karma

 * For developers who work with many builds, it's better to have one copy of
   bower/karma rather than reinstalling an extra 50mb for each build.
   If a system already has a copy of these, then don't forcibly download them.
   (If you really want extra copies, you can run "npm install" yourself.)
 * Documentation for composer is historically a bit inconsistent about
   whether to use "composer" or "composer.phar".  Work with either.
bin/npm_postinstall.sh [deleted file]
bin/setup.lib.sh
bin/setup.sh
package.json
tools/scripts/npm/postinstall.sh [new file with mode: 0644]
tools/scripts/npm/test.sh [new file with mode: 0644]