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

71 строка
2.4 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
},
Remove stray whitespace from package.json
2015-11-02 02:32:26 +03:00
"license": "MPL-2.0",
Bug 1234897 - Pin the version of nodejs used on Heroku https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
2015-12-23 22:07:12 +03:00
"engines": {
Bug 1419987 - Always use latest minor version of node.js (#2979) Since the node minor/patch versions are reliable enough that it's not worth the hassle of pinning to an exact version. This only affects Heroku/Travis, since Vagrant was already always using the latest 8 series release via the APT repo. This effectively upgrades node on Heroku/Travis from 8.9.0 to 8.9.1, since it's the latest release at the moment: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md#8.9.1 The yarn version specifier has been adjusted to use the `.x` format, which gives the same end result as the caret range, given Heroku doesn't cache binaries from one build to the next (only `node_modules`).
2017-11-27 19:40:54 +03:00
"node": "8.x",
"yarn": "1.x"
Bug 1234897 - Pin the version of nodejs used on Heroku https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
2015-12-23 22:07:12 +03:00
},
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 1408776 - Update ajv from 5.2.2 to 5.2.3 https://github.com/epoberezkin/ajv/compare/v5.2.2...v5.2.3
2017-10-16 00:06:26 +03:00
"ajv": "5.2.3",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"angular": "1.5.11",
"angular-cookies": "1.5.11",
"angular-local-storage": "0.5.2",
Bug 1408776 - Remove caret version ranges from package.json Since in a `yarn.lock` world they cause confusion with tooling as to what package version is actually in use.
2017-10-15 23:58:59 +03:00
"angular-marked": "1.2.2",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"angular-resource": "1.5.11",
"angular-route": "1.5.11",
"angular-sanitize": "1.5.11",
Bug 1364010 - Update angular-toarrayfilter from 1.0.1 to 1.0.2 The only change is the move of `karma` from angular-toarrayfilter's `dependencies` to `devDependencies`, which stops us unnecessarily pulling in an ancient version of karma, and the resultant security warnings.
2017-05-15 15:52:00 +03:00
"angular-toarrayfilter": "1.0.2",
Bug 1408776 - Update angular-ui-router from 0.4.2 to 0.4.3 https://github.com/angular-ui/ui-router/blob/0.4.3/CHANGELOG.md#043-2017-10-04
2017-10-15 23:04:31 +03:00
"angular-ui-router": "0.4.3",
Bug 1408100 - Upgrade to Bootstrap 4 This adds the upgrade to Bootstrap 4, and some basic changes and some CSS tweaks we needed to keep out UI consistent. The simpler changes are things like: * Classes that were renamed * Adding classes that are now needed (dropdown-item, etc) * Change an item from a button to a span * Changing order of items (modal header close button, etc) * CSS class syntax changes The other changes are lots of CSS padding, margin, font and other spacing tweaks.
2017-11-03 03:47:06 +03:00
"angular1-ui-bootstrap4": "2.4.22",
"bootstrap": "4.0.0-beta.2",
Bug 1408776 - Update deepmerge from 1.5.0 to 1.5.2 https://github.com/KyleAMathews/deepmerge/blob/v1.5.2/changelog.md#152
2017-10-15 23:07:08 +03:00
"deepmerge": "1.5.2",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"font-awesome": "4.7.0",
Bug 1387893 - Update JS dependencies Packages have been updated as follows: * `angular*`, `react*` and `enzyme`: Unchanged (latest patch version), for the same reasons as in bug 1364010. * all other packages have been bumped to their latest minor version. * caret version ranges have been converted to exact versions, for parity with the rest of the versions and to make it easier to identify which version is being used without having to view the lock file. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` Other bugs will handle the more involved `angular*`, `react*`, `enzyme` and `neutrino*` updates (see deps of bug 1364010).
2017-08-07 00:55:25 +03:00
"hawk": "6.0.2",
Bug 1364882 - Upgrade from JQuery 2.x to 3.x There were only two tiny issues that affected us: * $.bind has been deprecated, so it is a switch to $.on * Found a function that was dead code, so removed it
2017-05-27 00:03:21 +03:00
"jquery": "3.2.1",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"jquery.scrollto": "2.1.2",
Bug 1408776 - Update js-yaml from 3.9.1 to 3.10.0 https://github.com/nodeca/js-yaml/blob/3.10.0/CHANGELOG.md#3100--2017-09-10
2017-10-16 00:28:05 +03:00
"js-yaml": "3.10.0",
Bug 1408776 - Update json-e from 2.2.1 to 2.3.1 https://github.com/taskcluster/json-e/compare/v2.2.1...v2.3.1
2017-10-16 00:25:46 +03:00
"json-e": "2.3.1",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"json-schema-defaults": "0.3.0",
Bug 1336556 - Replace grunt build system with neutrino/webpack
2017-03-01 16:06:15 +03:00
"lodash": "4.17.4",
Bug 1387893 - Update JS dependencies Packages have been updated as follows: * `angular*`, `react*` and `enzyme`: Unchanged (latest patch version), for the same reasons as in bug 1364010. * all other packages have been bumped to their latest minor version. * caret version ranges have been converted to exact versions, for parity with the rest of the versions and to make it easier to identify which version is being used without having to view the lock file. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` Other bugs will handle the more involved `angular*`, `react*`, `enzyme` and `neutrino*` updates (see deps of bug 1364010).
2017-08-07 00:55:25 +03:00
"metrics-graphics": "2.11.0",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"mousetrap": "1.6.1",
Bug 1336556 - Replace grunt build system with neutrino/webpack
2017-03-01 16:06:15 +03:00
"neutrino": "4.3.1",
"neutrino-lint-base": "4.3.1",
"neutrino-preset-react": "4.2.3",
Bug 1408776 - Update ngreact from 0.4.1 to 0.5.0 https://github.com/ngReact/ngReact/releases/tag/v0.5.0
2017-10-16 00:19:12 +03:00
"ngreact": "0.5.0",
Bug 1387893 - Update JS dependencies Packages have been updated as follows: * `angular*`, `react*` and `enzyme`: Unchanged (latest patch version), for the same reasons as in bug 1364010. * all other packages have been bumped to their latest minor version. * caret version ranges have been converted to exact versions, for parity with the rest of the versions and to make it easier to identify which version is being used without having to view the lock file. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` Other bugs will handle the more involved `angular*`, `react*`, `enzyme` and `neutrino*` updates (see deps of bug 1364010).
2017-08-07 00:55:25 +03:00
"numeral": "2.0.6",
Bug 1408100 - Upgrade to Bootstrap 4 This adds the upgrade to Bootstrap 4, and some basic changes and some CSS tweaks we needed to keep out UI consistent. The simpler changes are things like: * Classes that were renamed * Adding classes that are now needed (dropdown-item, etc) * Change an item from a button to a span * Changing order of items (modal header close button, etc) * CSS class syntax changes The other changes are lots of CSS padding, margin, font and other spacing tweaks.
2017-11-03 03:47:06 +03:00
"popper.js": "1.12.6",
Bug 1364891 - Update from React 15.3 to 15.6 Also upgrade Enzyme from 2.7.1 to 3.1.1 Most notable change here is that React.PropTypes is now moved to a separate package and referenced just by PropTypes. So this needed some import and linting changes.
2017-11-11 01:23:45 +03:00
"prop-types": "15.6.0",
Bug 1336556 - Cache angular partials with webpack Load the contents of the various angular partials into the template cache at build time so that they don't need to be built separately.
2017-03-04 03:03:43 +03:00
"raw-loader": "0.5.1",
Bug 1364891 - Update from React 15.3 to 15.6 Also upgrade Enzyme from 2.7.1 to 3.1.1 Most notable change here is that React.PropTypes is now moved to a separate package and referenced just by PropTypes. So this needed some import and linting changes.
2017-11-11 01:23:45 +03:00
"react": "15.6.2",
"react-dom": "15.6.2",
Bug 1408776 - Update taskcluster-client from 2.5.0 to 2.5.4 https://github.com/taskcluster/taskcluster-client/compare/v2.5.0...v2.5.4
2017-10-15 23:09:09 +03:00
"taskcluster-client": "2.5.4"
travis change
2014-04-08 21:40:33 +04:00
},
Bug 1353014 - Move test/dev package.json dependencies to devDependencies Since they aren't required for the UI build, so don't need to be installed during the Heroku compile (which sets `NODE_ENV=production`).
2017-04-05 19:03:30 +03:00
"devDependencies": {
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"angular-mocks": "1.5.11",
Bug 1364891 - Update from React 15.3 to 15.6 Also upgrade Enzyme from 2.7.1 to 3.1.1 Most notable change here is that React.PropTypes is now moved to a separate package and referenced just by PropTypes. So this needed some import and linting changes.
2017-11-11 01:23:45 +03:00
"enzyme": "3.1.1",
"enzyme-adapter-react-15": "1.0.5",
"react-test-renderer": "15.6.2",
Bug 1353014 - Move test/dev package.json dependencies to devDependencies Since they aren't required for the UI build, so don't need to be installed during the Heroku compile (which sets `NODE_ENV=production`).
2017-04-05 19:03:30 +03:00
"istanbul-instrumenter-loader": "2.0.0",
Bug 1408776 - Update jasmine-core from 2.7.0 to 2.8.0 https://github.com/jasmine/jasmine/blob/v2.8.0/release_notes/2.8.0.md
2017-10-16 00:21:08 +03:00
"jasmine-core": "2.8.0",
Bug 1387893 - Update JS dependencies Packages have been updated as follows: * `angular*`, `react*` and `enzyme`: Unchanged (latest patch version), for the same reasons as in bug 1364010. * all other packages have been bumped to their latest minor version. * caret version ranges have been converted to exact versions, for parity with the rest of the versions and to make it easier to identify which version is being used without having to view the lock file. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` Other bugs will handle the more involved `angular*`, `react*`, `enzyme` and `neutrino*` updates (see deps of bug 1364010).
2017-08-07 00:55:25 +03:00
"karma-coverage-istanbul-reporter": "1.3.0",
Bug 1364010 - Update JS dependencies Packages have been updated as follows: * `angular*`: Latest patch version, since it doesn't follow semver. * `react*`: Latest patch version, since in 15.5 some obtrusive deprecation warnings were added, and `enzyme`'s peer-dependencies need adjusting too. * `enzyme`: Unchanged, since the newer minor version gives warnings. * all other packages have been bumped to their latest minor version. This was performed using: ``` sudo yarn global add npm-check-updates ncu --upgrade --upgradeAll --semverLevel minor ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/' ``` In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client` and `hawk` have been bumped to the latest major versions since their changelogs don't show any breaking changes that impact us. The lock file was then regenerated using: ``` rm -rf node_modules/ yarn.lock yarn install --no-bin-links ``` At some point later we'll want to perform the more involved `angular*`, `react*`, `enzyme`, `jquery` and `neutrino*` updates.
2017-05-11 13:14:21 +03:00
"karma-firefox-launcher": "1.0.1",
Bug 1353014 - Move test/dev package.json dependencies to devDependencies Since they aren't required for the UI build, so don't need to be installed during the Heroku compile (which sets `NODE_ENV=production`).
2017-04-05 19:03:30 +03:00
"karma-jasmine": "1.1.0",
Bug 1364891 - Update from React 15.3 to 15.6 Also upgrade Enzyme from 2.7.1 to 3.1.1 Most notable change here is that React.PropTypes is now moved to a separate package and referenced just by PropTypes. So this needed some import and linting changes.
2017-11-11 01:23:45 +03:00
"neutrino-preset-karma": "4.2.1"
Bug 1353014 - Move test/dev package.json dependencies to devDependencies Since they aren't required for the UI build, so don't need to be installed during the Heroku compile (which sets `NODE_ENV=production`).
2017-04-05 19:03:30 +03:00
},
travis change
2014-04-08 21:40:33 +04:00
"scripts": {
Bug 1351907 - Improve yarn script Windows compatibility (#2863) Typically the `package.json` commands call scripts that exist in the top-level `node_modules/.bin/` directory, which are (a) already on `PATH` when invoked by yarn, and (b) on Windows have `.cmd` script shims that work around Windows' lack of shebang support. However due to symlinks being problematic inside Virtualbox, we have to use `--no-bin-links` with `yarn install`, which means the top-level `.bin/` directory doesn't exist. As such, the `<package>/bin/` scripts have to be used directly, which require prefixing with `node` to work around lack of shebang support on Windows. See: https://shapeshed.com/writing-cross-platform-node/#scripts-in-package-json Note that even with these changes, the `start:stage` command will not work due to the environment variable prefix. This will be solved by the switch to newer Neutrino, which supports setting environment variables using the `--options` command line parameter instead.
2017-10-23 19:29:41 +03:00
"build": "node ./node_modules/neutrino/bin/neutrino build --presets ./neutrino-custom/production.js",
"lint": "node ./node_modules/eslint/bin/eslint.js --ext .js,.jsx ui/",
"start": "node ./node_modules/neutrino/bin/neutrino start --presets ./neutrino-custom/development.js",
"start:local": "node ./node_modules/neutrino/bin/neutrino start --presets ./neutrino-custom/local-watch.js",
"start:stage": "SERVICE_DOMAIN=https://treeherder.allizom.org node ./node_modules/neutrino/bin/neutrino start --presets ./neutrino-custom/development.js",
"test": "node ./node_modules/neutrino/bin/neutrino test --presets ./neutrino-custom/test.js",
"test:watch": "node ./node_modules/neutrino/bin/neutrino test --watch --presets ./neutrino-custom/test.js"
travis change
2014-04-08 21:40:33 +04:00
}
}