mozilla
/
treeherder
зеркало из https://github.com/mozilla/treeherder.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
treeherder/package.json

37 строки
1.0 KiB
JSON
Исходник Обычный вид История

travis change
2014-04-08 21:40:33 +04:00
{
Bug 1170330 - Update treeherder package.json post repo-merge
2015-06-02 00:40:08 +03:00
"name": "treeherder",
"description": "Mozilla Treeherder reporting dashboard",
Bug 1063483 - Define repository in package.json to suppress npm warning
2014-09-05 16:20:50 +04:00
"repository": {
"type": "git",
Bug 1056877 - Stop using/referring to the separate treeherder-ui repo Since it has now been merged into this one.
2015-05-18 17:47:06 +03:00
"url": "https://github.com/mozilla/treeherder.git"
Bug 1063483 - Define repository in package.json to suppress npm warning
2014-09-05 16:20:50 +04:00
},
Bug 1210738 - Declare the license type in package.json To suppress the warning shown when using `npm install`.
2015-10-06 15:16:04 +03:00
"license" : "MPL-2.0",
Bug 1206108 - Separate `grunt build` npm packages from those for testing To run grunt build as part of deploy, we're going to need to npm install the dependencies required for it. However we do not need to install the testing related packages, so by splitting the two between `dependencies` and `devDependencies` we'll have more control. eg: `npm install --production` will only install those under `dependencies`. See: https://docs.npmjs.com/files/package.json#dependencies https://docs.npmjs.com/files/package.json#devdependencies https://docs.npmjs.com/misc/config#production
2015-09-18 17:16:53 +03:00
"dependencies": {
Bug 1145083 - Update grunt node packages & pin to specific versions We were previously using '~' (which allows for N.N.*) and '^' (which allows for N.*.*) for the grunt node package version numbers. This meant that each person running grunt build could end up with different output, since the versions were not pinned. Instead, all packages are now pinned to a specific version - the latest currently available (which in many cases is not far off the version someone running |npm install| in a clean repo would have gotten anyway, due to the use of '^' and '~').
2015-05-20 16:51:31 +03:00
"grunt": "0.4.5",
"grunt-angular-templates": "0.5.7",
"grunt-cache-busting": "0.0.11",
Bug 1201523 - Add grunt-cli to local dependencies list Normally grunt-cli (a wrapper around grunt to allow it to be easily run from the command line) would be installed globally, so that it is on the PATH. However to save having to do this on prod/Heroku/Travis, we install it locally - and it will then be available via: `./node_modules/.bin/grunt` ...or else via just `grunt`, if referenced inside a package.json scripts section.
2015-09-30 19:52:35 +03:00
"grunt-cli": "0.1.13",
Bug 1145083 - Update grunt node packages & pin to specific versions We were previously using '~' (which allows for N.N.*) and '^' (which allows for N.*.*) for the grunt node package version numbers. This meant that each person running grunt build could end up with different output, since the versions were not pinned. Instead, all packages are now pinned to a specific version - the latest currently available (which in many cases is not far off the version someone running |npm install| in a clean repo would have gotten anyway, due to the use of '^' and '~').
2015-05-20 16:51:31 +03:00
"grunt-contrib-clean": "0.6.0",
"grunt-contrib-concat": "0.5.1",
Bug 1206670 - Update dependencies for grunt build to latest versions Package Current Latest grunt-contrib-cssmin 0.12.3 0.14.0 grunt-contrib-copy 0.8.0 0.8.1 grunt-contrib-uglify 0.9.1 0.9.2 grunt-usemin 3.0.0 3.1.1
2015-09-21 14:24:03 +03:00
"grunt-contrib-copy": "0.8.1",
"grunt-contrib-cssmin": "0.14.0",
"grunt-contrib-uglify": "0.9.2",
"grunt-usemin": "3.1.1",
Bug 1206108 - Pin load-grunt-tasks to v3.2.0 The previous value of "^3.2.0" is equivalent to "4 > version >= 3.2.0". We should pin to a specific version to stop deployments breaking if a new release doesn't behave as expected. See: https://nodesource.com/blog/semver-tilde-and-caret We should also do the same for devDependencies, but let's do that in another bug, since it doesn't affect production.
2015-09-18 19:47:11 +03:00
"load-grunt-tasks": "3.2.0"
Bug 1206108 - Separate `grunt build` npm packages from those for testing To run grunt build as part of deploy, we're going to need to npm install the dependencies required for it. However we do not need to install the testing related packages, so by splitting the two between `dependencies` and `devDependencies` we'll have more control. eg: `npm install --production` will only install those under `dependencies`. See: https://docs.npmjs.com/files/package.json#dependencies https://docs.npmjs.com/files/package.json#devdependencies https://docs.npmjs.com/misc/config#production
2015-09-18 17:16:53 +03:00
},
"devDependencies": {
Bug 1183367 - Add a grunt target to run eslint on JS frontend
2015-07-14 20:33:07 +03:00
"grunt-eslint": "16.0.0",
Bug 1206670 - Update grunt-html-angular-validate to v0.5.2 It's not yet used in Travis, but we'll hopefully start using it in the future.
2015-09-21 16:13:02 +03:00
"grunt-html-angular-validate": "0.5.2",
Bug 1206670 - Update karma to v0.13.10 and karma-jasmine to v0.3.6 As of karma-jasmine 0.3.0, the jasmine library is not bundled with karma-jasmine, and so jasmine-core has to be installed separately. jasmine-jquery also has to be updated, since the old version was not compatible. A duplicate jasmine-jquery file that was outside of the tests vendor directory has also been removed.
2015-09-21 16:16:26 +03:00
"jasmine-core": "2.3.4",
"karma": "0.13.10",
Bug 1206670 - Pin packages in devDependencies to explicit versions To avoid Travis failing if new package authors don't follow semver and break things in a point release. This is effectively a no-op, compared to a clean install using the prior package.json.
2015-09-19 17:16:18 +03:00
"karma-coverage": "0.5.2",
"karma-firefox-launcher": "0.1.6",
Bug 1206670 - Update karma to v0.13.10 and karma-jasmine to v0.3.6 As of karma-jasmine 0.3.0, the jasmine library is not bundled with karma-jasmine, and so jasmine-core has to be installed separately. jasmine-jquery also has to be updated, since the old version was not compatible. A duplicate jasmine-jquery file that was outside of the tests vendor directory has also been removed.
2015-09-21 16:16:26 +03:00
"karma-jasmine": "0.3.6",
Bug 1206670 - Pin packages in devDependencies to explicit versions To avoid Travis failing if new package authors don't follow semver and break things in a point release. This is effectively a no-op, compared to a clean install using the prior package.json.
2015-09-19 17:16:18 +03:00
"karma-junit-reporter": "0.3.4",
"karma-ng-scenario": "0.1.0"
travis change
2014-04-08 21:40:33 +04:00
},
"scripts": {
Bug 1056877 - Update UI path references after directory moves As part of merging the UI repo into this one, the following directory moves were performed: webapp/app/ -> ui/ webapp/test/ -> tests/ui/ webapp/config/ -> tests/ui/config/ webapp/scripts/ -> tests/ui/scripts/ webapp/scripts/web-server.js -> web-server.js
2015-05-18 18:00:59 +03:00
"test": "karma start tests/ui/config/karma.conf.js --single-run --browsers Firefox"
travis change
2014-04-08 21:40:33 +04:00
}
}