diff options
| author | Michael Krotscheck <krotscheck@gmail.com> | 2015-06-03 15:40:06 -0700 |
|---|---|---|
| committer | Michael Krotscheck <krotscheck@gmail.com> | 2015-06-05 08:16:22 -0700 |
| commit | 4ffd55c7c92d805e3dbb8ae5814eff5309113c5c (patch) | |
| tree | 03caa0684bba24ccc34461f8956303588958c167 /package.json | |
| parent | e819dac5c98297d71848f3d170b72f2226f74cdc (diff) | |
| download | horizon-4ffd55c7c92d805e3dbb8ae5814eff5309113c5c.tar.gz | |
Added karma-cli to package.json
Turns out that npm runs a little like venv's do, in that it can
install executables in its own path. This adds the karma-cli
executable into the npm path, and removes additional extraneous
content from the package.json file.
Change-Id: Ib25553956a9757ecbb1ee7ce722f3646ededc035
Diffstat (limited to 'package.json')
| -rw-r--r-- | package.json | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/package.json b/package.json index 0a101010e..4c283bfa8 100644 --- a/package.json +++ b/package.json @@ -9,14 +9,15 @@ "jasmine-core": "2.2.0", "karma": "0.12.31", "karma-chrome-launcher": "0.1.8", + "karma-cli": "0.0.4", "karma-coverage": "0.3.1", "karma-jasmine": "0.3.5", "karma-ng-html2js-preprocessor": "0.1.2", "karma-phantomjs-launcher": "0.2.0", - "phantomjs": "^1.9.17" + "phantomjs": "1.9.17" }, "scripts": { - "test": "node node_modules/karma/bin/karma start horizon/karma.conf.js --single-run && node node_modules/karma/bin/karma start openstack_dashboard/karma.conf.js --single-run" + "test": "karma start horizon/karma.conf.js --single-run && karma start openstack_dashboard/karma.conf.js --single-run" }, "dependencies": {} } |