Blame: package.json - angular/angular.js

chore(package.json): add simple package.json with npm dependencies

2012-05-22 23:39:07 -07:00

chore(package.json): fix name to work with latest NPM

2013-07-13 17:20:56 -07:00

								  "name": "angularjs",

							

chore(npm): add the license to package.json This removes a warning when executing npm install. Closes #12111

2015-06-15 00:21:16 +02:00

								  "license": "MIT",

							

chore(package.json): update docs app to use latest version of AngularJS

2018-05-21 10:19:44 +01:00

								  "branchVersion": "^1.7.0",

							

chore(package): update dist-tag for master/1.7

2016-12-08 13:56:34 +00:00

								  "branchPattern": "1.7.*",

							

chore(package.json): change distTag to "latest"

2018-05-09 19:38:48 +02:00

								  "distTag": "latest",

							

fix(package.json): add a repository field The `npm install` command complains about the missing repository field. Closes #3674

2013-08-20 16:49:43 +02:00

								  "repository": {

							

chore(npm/travis): upgrade to npm 2.5 and require it via package.json currently karma's dependencies don't install on node 0.12 or io.js so we'll just update npm in hope that that this will mitigate "cb() never called!" erorrs. See: https://travis-ci.org/angular/angular.js/jobs/51474043#L2181

2015-02-19 22:30:25 -08:00

								  "engines": {

							

build(*): update Node from 6 to 8, update Yarn Angular (2+) switched to Node 8 and so should we. Closes #16360 Ref angular/angular#20807 Ref angular/angular#20832

2017-12-07 19:26:32 +01:00

								    "node": "^8.9.1",

							

chore(dependencies): USE YARN (and node 6)

2016-11-29 13:16:30 +00:00

								    "grunt": "^1.2.0"

							

chore(npm/travis): upgrade to npm 2.5 and require it via package.json currently karma's dependencies don't install on node 0.12 or io.js so we'll just update npm in hope that that this will mitigate "cb() never called!" erorrs. See: https://travis-ci.org/angular/angular.js/jobs/51474043#L2181

2015-02-19 22:30:25 -08:00

},

chore(check-node-modules): make check/reinstall node_modules work across platforms The previous implementations (based on shell scripts) threw errors on Windows, because it was not able to `rm -rf` 'node_modules' (due to the 255 character limit in file-paths). This implementation works consistently across platforms and is heavily based on 'https://github.com/angular/angular/blob/3b9c08676a4c921bbfa847802e08566fb601ba7a/tools/npm/check-node-modules.js'. Fixes #11143 Closes #11353 Closes #12792

2015-09-09 03:27:45 +03:00

								  "scripts": {

							

chore(i18n): fix up i18n testing tools

2016-01-26 10:05:13 +00:00

								    "commit": "git-cz",

							

feat(ngParseExt): New ngParseExt module New ngParseExt module Including this module into an application will extend $parse to allow identifiers following ES6 identifiers

2015-09-20 21:29:59 +02:00

								    "test-i18n": "jasmine-node i18n/spec",

							

chore(jenkins): fix yarn and grunt installation

2016-12-07 10:50:24 +00:00

								    "test-i18n-ucd": "jasmine-node i18n/ucd/spec",

							

chore(check-node-modules): make check/reinstall node_modules work across platforms The previous implementations (based on shell scripts) threw errors on Windows, because it was not able to `rm -rf` 'node_modules' (due to the 255 character limit in file-paths). This implementation works consistently across platforms and is heavily based on 'https://github.com/angular/angular/blob/3b9c08676a4c921bbfa847802e08566fb601ba7a/tools/npm/check-node-modules.js'. Fixes #11143 Closes #11353 Closes #12792

2015-09-09 03:27:45 +03:00

},

chore(package.json): use `devDependencies` instead of `dependencies`

2013-05-18 11:41:27 -04:00

								  "devDependencies": {

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "angular-benchpress": "0.x.x",

							

chore(docs): don't use bower for docs dependencies

2016-12-01 13:26:51 +00:00

								    "bootstrap": "3.1.1",

							

chore(browserstack): Update browserstacktunnel-wrapper, fix options Only the latest version of the package works correctly (the backend for it at BrowserStack is not versioned) and the options have changed in the new version of the package. Also, iOS 8.0 is no longer available on BrowserStack, only 8.3 is. Instead, this commit changes it to 9.3 as we shouldn't be testing on 8 anymore anyway. Closes #15892

2017-04-12 13:20:43 +02:00

								    "browserstacktunnel-wrapper": "2.0.0",

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "canonical-path": "0.0.2",

							

chore(deps): add changez

2016-10-26 17:21:57 +01:00

								    "changez": "^2.1.1",

							

chore(deps): update changez-angular version

2016-12-23 10:52:32 +00:00

								    "changez-angular": "^2.1.2",

							

chore(testing): bump protractor to version 1.6.0

2015-01-08 14:48:26 -08:00

								    "cheerio": "^0.17.0",

							

chore(package.json): add commitizen, adapter and npm script Closes #13194

2015-10-28 12:38:21 -04:00

								    "commitizen": "^2.3.0",

							

chore(travis): add commitplease validation to ci-checks This will provide feedback to contributors without getting in the way of writing invalid commit messages locally. The git hook integration is turned off. Committers who push directly to the repo can be expected to use correct commit messages ;) Most changes go through PRs anyway. Note that "Merge commit" messages and everything starting with "WIP" is always allowed by commitplease. Follow issue https://github.com/jzaefferer/commitplease/issues/101 for more info. Related to #14888 Closes #16097

2017-07-12 12:02:18 +02:00

								    "commitplease": "^2.7.10",

							

chore(*): use binaries from node_modules/.bin Closes #15071

2016-09-01 20:42:03 +02:00

								    "cross-spawn": "^4.0.0",

							

chore(package.json): add commitizen, adapter and npm script Closes #13194

2015-10-28 12:38:21 -04:00

								    "cz-conventional-changelog": "1.1.4",

							

chore(docs): update to dgeni-0.4.0 * update package with new services and computeId config * generateIndexPagesProcessor was not using log * use StringMap not ES6-shim Map in errorNamespaceMap * remove unused dependencies from generateErrorDocsProcessor * ensure generatePagesDataProcessor adds its doc to the collection * debugDumpProcessor was moved to dgeni-packages

2014-09-12 23:04:35 +01:00

								    "dgeni": "^0.4.0",

							

chore(*): update dgeni-packages (and other devDependencies) `dgeni-packages` prior to version 0.16.3 specified `engine.yarn: '^0.17.9'`, which was unnecessarily strict and would cause any task to fail if someone had a yarn version >=0.18.0. Other devDependencies were also updated (because why not). Closes #15600

2017-01-11 12:52:48 +02:00

								    "dgeni-packages": "^0.16.4",

							

chore(eslint): allow ES6 for node scripts

2018-02-12 12:26:32 +01:00

								    "eslint-plugin-promise": "^3.6.0",

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "event-stream": "~3.1.0",

							

chore(build): add a validation step for angularFiles Closes #13553

2015-12-15 11:46:50 -08:00

								    "glob": "^6.0.1",

							

chore(docs): don't use bower for docs dependencies

2016-12-01 13:26:51 +00:00

								    "google-code-prettify": "1.0.1",

							

chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt.

2016-07-20 00:54:17 +02:00

								    "grunt": "^1.0.1",

							

chore(Gruntfile.js, package.json): use load-grunt-tasks and move grunt-contrib-jshint into devDependencies Closes #6085

2014-02-01 23:14:07 -08:00

								    "grunt-ddescribe-iit": "~0.0.1",

							

chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952

2016-07-20 15:45:04 +02:00

								    "grunt-eslint": "^19.0.0",

							

chore(Gruntfile.js, package.json): use load-grunt-tasks and move grunt-contrib-jshint into devDependencies Closes #6085

2014-02-01 23:14:07 -08:00

								    "grunt-merge-conflict": "~0.0.1",

							

chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt.

2016-07-20 00:54:17 +02:00

								    "grunt-shell": "^1.3.0",

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "gulp": "~3.8.0",

							

chore(docs): minify javascript

2014-09-24 15:01:20 +01:00

								    "gulp-concat": "^2.4.1",

							

chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952

2016-07-20 15:45:04 +02:00

								    "gulp-eslint": "^3.0.1",

							

chore(docs): minify javascript

2014-09-24 15:01:20 +01:00

								    "gulp-foreach": "0.0.1",

							

chore(bower): refactor bower usage The gulp bower task in the docs app was never actually running since it couldn't find the bower.json file and was silently failing. Updating to a newer bower highlighted this issue. This commit moves the docs app specific bower components into the docs folder. There are only jquery and closure compiler related components in the project folder now. It also improves the gulp bower task to provide better feedback of progress and errors.

2014-09-08 10:14:17 +01:00

								    "gulp-util": "^3.0.1",

							

chore(node): update jasmine to 2.8.0, and adjust tests

2018-01-05 21:35:26 +01:00

								    "jasmine-core": "^2.8.0",

							

chore(i18n): fix up i18n testing tools

2016-01-26 10:05:13 +00:00

								    "jasmine-node": "^2.0.0",

							

chore(package.json): update jasmine-reporters to 2.2.0

2016-07-07 15:26:18 +02:00

								    "jasmine-reporters": "^2.2.0",

							

chore(*): get rid of Bower in favor of Yarn aliases & checked-in packages Bower was used to install multiple versions of jQuery which is now handled using Yarn aliases. The remaining two packages, closure-compiler and ng-closure-compiler were installed from zip files which is not supported by Yarn (see https://github.com/yarnpkg/yarn/issues/1483); the first of them exists on npm as the google-closure-compiler but only versions newer than we used are published and they don't work with ng-closure-compiler so - instead - both were checked in to the repository. Fixes #16268 Fixes #14961 Ref yarnpkg/yarn#1483

2017-12-27 19:16:46 +01:00

								    "jquery": "3.2.1",

							

chore(node): update karma to 2.0.0 Also reduce karma log level on Travis to INFO. Before, the log level was DEBUG, but it seems that prior to karma 2.0.0, the debug messages were not outoput on Karma, so this simply restores the status quo (and prevents cluttering the log).

2018-01-05 22:05:15 +01:00

								    "karma": "^2.0.0",

							

chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966

2017-05-06 17:50:42 +02:00

								    "karma-browserstack-launcher": "^1.2.0",

							

chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407

2018-01-15 13:07:45 +01:00

								    "karma-edge-launcher": "^0.4.2",

							

chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966

2017-05-06 17:50:42 +02:00

								    "karma-firefox-launcher": "^1.0.1",

							

chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407

2018-01-15 13:07:45 +01:00

								    "karma-ie-launcher": "^1.0.0",

							

chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966

2017-05-06 17:50:42 +02:00

								    "karma-jasmine": "^1.1.0",

							

chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407

2018-01-15 13:07:45 +01:00

								    "karma-safari-launcher": "^1.0.0",

							

chore(node): update karma-sauce-launcher Related to #14961 Closes #16281

2017-10-16 11:51:00 +02:00

								    "karma-sauce-launcher": "^1.2.0",

							

chore(package.json): update Karma & BrowserStack-related packages

2016-08-05 20:24:42 +02:00

								    "karma-script-launcher": "^1.0.0",

							

chore(travis): use "karma-spec-reporter" dots reporter creates lots of empty space that makes it tedious to scroll through the logs. "Spec" is configured to only report on failures.

2017-06-10 23:36:38 +02:00

								    "karma-spec-reporter": "^0.0.31",

							

chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt.

2016-07-20 00:54:17 +02:00

								    "load-grunt-tasks": "^3.5.0",

							

chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571

2014-10-11 21:58:38 +02:00

								    "lodash": "~2.4.1",

							

chore(npm): use require.resolve when possible to avoid hard coded module paths

2015-11-16 16:26:49 -08:00

								    "log4js": "^0.6.27",

							

chore(docs): don't use bower for docs dependencies

2016-12-01 13:26:51 +00:00

								    "lunr": "^0.7.2",

							

chore(doc-gen): new docs chore(doc-gen): implement dgeni

2014-02-12 22:47:42 +00:00

								    "marked": "~0.3.0",

							

chore(clean-shrinkwrap): add a utility to clean up the shrinkwrap file This is to deal with https://github.com/npm/npm/issues/3581 See the previous commit for more info. Closes #6672

2014-03-13 18:30:17 +00:00

								    "node-html-encoder": "0.0.2",

							

chore(utils): install npm-run to simplify scripts

2016-11-28 11:19:59 +00:00

								    "npm-run": "^4.1.0",

							

chore(docs): don't use bower for docs dependencies

2016-12-01 13:26:51 +00:00

								    "open-sans-fontface": "^1.4.0",

							

chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571

2014-10-11 21:58:38 +02:00

								    "promises-aplus-tests": "~2.1.0",

							

chore(*): update protractor Update protractor to latest 5.1.2 to make it work with Chrome 58 on Jenkins. This protractor version is not compatible with FF 53 and directConnect, but this should be irrelevant as Travis does not use directConnect and on Jenkins we don't test FF. Closes #15991

2017-05-17 09:22:34 +02:00

								    "protractor": "^5.1.2",

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "q": "~1.0.0",

							

chore(perf): add event delegation benchmark

2014-07-31 06:26:10 -07:00

								    "qq": "^0.3.5",

							

chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571

2014-10-11 21:58:38 +02:00

								    "rewire": "~2.1.0",

							

feat(ngParseExt): New ngParseExt module New ngParseExt module Including this module into an application will extend $parse to allow identifiers following ES6 identifiers

2015-09-20 21:29:59 +02:00

								    "sax": "^1.1.1",

							

chore(npm): use require.resolve when possible to avoid hard coded module paths

2015-11-16 16:26:49 -08:00

								    "selenium-webdriver": "^2.53.1",

							

chore(node): update semver Closes #16396

2018-01-09 12:57:45 +01:00

								    "semver": "^5.4.1",

							

chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt.

2016-07-20 00:54:17 +02:00

								    "serve-favicon": "^2.3.0",

							

chore(package.json): update to latest version of shelljs

2016-11-11 19:47:28 +00:00

								    "shelljs": "^0.7.5",

							

chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions.

2014-09-08 09:50:47 +01:00

								    "sorted-object": "^1.0.0",

							

chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952

2016-07-20 15:45:04 +02:00

								    "stringmap": "^0.2.2"

							

chore(NPM): Add license info

2013-03-27 00:12:45 -07:00

},

chore(package.json): add commitizen, adapter and npm script Closes #13194

2015-10-28 12:38:21 -04:00

								  "dependencies": {},

							

chore(travis): add commitplease validation to ci-checks This will provide feedback to contributors without getting in the way of writing invalid commit messages locally. The git hook integration is turned off. Committers who push directly to the repo can be expected to use correct commit messages ;) Most changes go through PRs anyway. Note that "Merge commit" messages and everything starting with "WIP" is always allowed by commitplease. Follow issue https://github.com/jzaefferer/commitplease/issues/101 for more info. Related to #14888 Closes #16097

2017-07-12 12:02:18 +02:00

								  "commitplease": {

							

chore(package.json): add commitizen, adapter and npm script Closes #13194

2015-10-28 12:38:21 -04:00

								  "config": {

							

chore(node): update karma-sauce-launcher Related to #14961 Closes #16281

2017-10-16 11:51:00 +02:00

}

chore(package.json): add simple package.json with npm dependencies 2012-05-22 23:39:07 -07:00			`{`
chore(package.json): fix name to work with latest NPM 2013-07-13 17:20:56 -07:00			`"name": "angularjs",`
chore(npm): add the license to package.json This removes a warning when executing npm install. Closes #12111 2015-06-15 00:21:16 +02:00			`"license": "MIT",`
chore(package.json): update docs app to use latest version of AngularJS 2018-05-21 10:19:44 +01:00			`"branchVersion": "^1.7.0",`
chore(package): update dist-tag for master/1.7 2016-12-08 13:56:34 +00:00			`"branchPattern": "1.7.*",`
chore(package.json): change distTag to "latest" 2018-05-09 19:38:48 +02:00			`"distTag": "latest",`
fix(package.json): add a repository field The `npm install` command complains about the missing repository field. Closes #3674 2013-08-20 16:49:43 +02:00			`"repository": {`
			`"type": "git",`
			`"url": "https://github.com/angular/angular.js.git"`
			`},`
chore(npm/travis): upgrade to npm 2.5 and require it via package.json currently karma's dependencies don't install on node 0.12 or io.js so we'll just update npm in hope that that this will mitigate "cb() never called!" erorrs. See: https://travis-ci.org/angular/angular.js/jobs/51474043#L2181 2015-02-19 22:30:25 -08:00			`"engines": {`
build(*): update Node from 6 to 8, update Yarn Angular (2+) switched to Node 8 and so should we. Closes #16360 Ref angular/angular#20807 Ref angular/angular#20832 2017-12-07 19:26:32 +01:00			`"node": "^8.9.1",`
			`"yarn": ">=1.3.2",`
chore(dependencies): USE YARN (and node 6) 2016-11-29 13:16:30 +00:00			`"grunt": "^1.2.0"`
chore(npm/travis): upgrade to npm 2.5 and require it via package.json currently karma's dependencies don't install on node 0.12 or io.js so we'll just update npm in hope that that this will mitigate "cb() never called!" erorrs. See: https://travis-ci.org/angular/angular.js/jobs/51474043#L2181 2015-02-19 22:30:25 -08:00			`},`
chore(check-node-modules): make check/reinstall node_modules work across platforms The previous implementations (based on shell scripts) threw errors on Windows, because it was not able to `rm -rf` 'node_modules' (due to the 255 character limit in file-paths). This implementation works consistently across platforms and is heavily based on 'https://github.com/angular/angular/blob/3b9c08676a4c921bbfa847802e08566fb601ba7a/tools/npm/check-node-modules.js'. Fixes #11143 Closes #11353 Closes #12792 2015-09-09 03:27:45 +03:00			`"scripts": {`
chore(i18n): fix up i18n testing tools 2016-01-26 10:05:13 +00:00			`"commit": "git-cz",`
feat(ngParseExt): New ngParseExt module New ngParseExt module Including this module into an application will extend $parse to allow identifiers following ES6 identifiers 2015-09-20 21:29:59 +02:00			`"test-i18n": "jasmine-node i18n/spec",`
chore(jenkins): fix yarn and grunt installation 2016-12-07 10:50:24 +00:00			`"test-i18n-ucd": "jasmine-node i18n/ucd/spec",`
			`"grunt": "grunt"`
chore(check-node-modules): make check/reinstall node_modules work across platforms The previous implementations (based on shell scripts) threw errors on Windows, because it was not able to `rm -rf` 'node_modules' (due to the 255 character limit in file-paths). This implementation works consistently across platforms and is heavily based on 'https://github.com/angular/angular/blob/3b9c08676a4c921bbfa847802e08566fb601ba7a/tools/npm/check-node-modules.js'. Fixes #11143 Closes #11353 Closes #12792 2015-09-09 03:27:45 +03:00			`},`
chore(package.json): use `devDependencies` instead of `dependencies` 2013-05-18 11:41:27 -04:00			`"devDependencies": {`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"angular-benchpress": "0.x.x",`
			`"benchmark": "1.x.x",`
chore(docs): don't use bower for docs dependencies 2016-12-01 13:26:51 +00:00			`"bootstrap": "3.1.1",`
chore(browserstack): Update browserstacktunnel-wrapper, fix options Only the latest version of the package works correctly (the backend for it at BrowserStack is not versioned) and the options have changed in the new version of the package. Also, iOS 8.0 is no longer available on BrowserStack, only 8.3 is. Instead, this commit changes it to 9.3 as we shouldn't be testing on 8 anymore anyway. Closes #15892 2017-04-12 13:20:43 +02:00			`"browserstacktunnel-wrapper": "2.0.0",`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"canonical-path": "0.0.2",`
chore(deps): add changez 2016-10-26 17:21:57 +01:00			`"changez": "^2.1.1",`
chore(deps): update changez-angular version 2016-12-23 10:52:32 +00:00			`"changez-angular": "^2.1.2",`
chore(testing): bump protractor to version 1.6.0 2015-01-08 14:48:26 -08:00			`"cheerio": "^0.17.0",`
chore(package.json): add commitizen, adapter and npm script Closes #13194 2015-10-28 12:38:21 -04:00			`"commitizen": "^2.3.0",`
chore(travis): add commitplease validation to ci-checks This will provide feedback to contributors without getting in the way of writing invalid commit messages locally. The git hook integration is turned off. Committers who push directly to the repo can be expected to use correct commit messages ;) Most changes go through PRs anyway. Note that "Merge commit" messages and everything starting with "WIP" is always allowed by commitplease. Follow issue https://github.com/jzaefferer/commitplease/issues/101 for more info. Related to #14888 Closes #16097 2017-07-12 12:02:18 +02:00			`"commitplease": "^2.7.10",`
chore(*): use binaries from node_modules/.bin Closes #15071 2016-09-01 20:42:03 +02:00			`"cross-spawn": "^4.0.0",`
chore(package.json): add commitizen, adapter and npm script Closes #13194 2015-10-28 12:38:21 -04:00			`"cz-conventional-changelog": "1.1.4",`
chore(docs): update to dgeni-0.4.0 * update package with new services and computeId config * generateIndexPagesProcessor was not using log * use StringMap not ES6-shim Map in errorNamespaceMap * remove unused dependencies from generateErrorDocsProcessor * ensure generatePagesDataProcessor adds its doc to the collection * debugDumpProcessor was moved to dgeni-packages 2014-09-12 23:04:35 +01:00			`"dgeni": "^0.4.0",`
chore(*): update dgeni-packages (and other devDependencies) `dgeni-packages` prior to version 0.16.3 specified `engine.yarn: '^0.17.9'`, which was unnecessarily strict and would cause any task to fail if someone had a yarn version >=0.18.0. Other devDependencies were also updated (because why not). Closes #15600 2017-01-11 12:52:48 +02:00			`"dgeni-packages": "^0.16.4",`
chore(eslint): allow ES6 for node scripts 2018-02-12 12:26:32 +01:00			`"eslint-plugin-promise": "^3.6.0",`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"event-stream": "~3.1.0",`
chore(build): add a validation step for angularFiles Closes #13553 2015-12-15 11:46:50 -08:00			`"glob": "^6.0.1",`
chore(docs): don't use bower for docs dependencies 2016-12-01 13:26:51 +00:00			`"google-code-prettify": "1.0.1",`
chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt. 2016-07-20 00:54:17 +02:00			`"grunt": "^1.0.1",`
			`"grunt-bump": "^0.8.0",`
			`"grunt-cli": "^1.2.0",`
			`"grunt-contrib-clean": "^1.0.0",`
			`"grunt-contrib-compress": "^1.3.0",`
			`"grunt-contrib-connect": "^1.0.2",`
			`"grunt-contrib-copy": "^1.0.0",`
chore(Gruntfile.js, package.json): use load-grunt-tasks and move grunt-contrib-jshint into devDependencies Closes #6085 2014-02-01 23:14:07 -08:00			`"grunt-ddescribe-iit": "~0.0.1",`
chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952 2016-07-20 15:45:04 +02:00			`"grunt-eslint": "^19.0.0",`
chore(Gruntfile.js, package.json): use load-grunt-tasks and move grunt-contrib-jshint into devDependencies Closes #6085 2014-02-01 23:14:07 -08:00			`"grunt-merge-conflict": "~0.0.1",`
chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt. 2016-07-20 00:54:17 +02:00			`"grunt-shell": "^1.3.0",`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"gulp": "~3.8.0",`
chore(docs): minify javascript 2014-09-24 15:01:20 +01:00			`"gulp-concat": "^2.4.1",`
chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952 2016-07-20 15:45:04 +02:00			`"gulp-eslint": "^3.0.1",`
chore(docs): minify javascript 2014-09-24 15:01:20 +01:00			`"gulp-foreach": "0.0.1",`
			`"gulp-rename": "^1.2.0",`
			`"gulp-sourcemaps": "^1.2.2",`
			`"gulp-uglify": "^1.0.1",`
chore(bower): refactor bower usage The gulp bower task in the docs app was never actually running since it couldn't find the bower.json file and was silently failing. Updating to a newer bower highlighted this issue. This commit moves the docs app specific bower components into the docs folder. There are only jquery and closure compiler related components in the project folder now. It also improves the gulp bower task to provide better feedback of progress and errors. 2014-09-08 10:14:17 +01:00			`"gulp-util": "^3.0.1",`
chore(node): update jasmine to 2.8.0, and adjust tests 2018-01-05 21:35:26 +01:00			`"jasmine-core": "^2.8.0",`
chore(i18n): fix up i18n testing tools 2016-01-26 10:05:13 +00:00			`"jasmine-node": "^2.0.0",`
chore(package.json): update jasmine-reporters to 2.2.0 2016-07-07 15:26:18 +02:00			`"jasmine-reporters": "^2.2.0",`
chore(*): get rid of Bower in favor of Yarn aliases & checked-in packages Bower was used to install multiple versions of jQuery which is now handled using Yarn aliases. The remaining two packages, closure-compiler and ng-closure-compiler were installed from zip files which is not supported by Yarn (see https://github.com/yarnpkg/yarn/issues/1483); the first of them exists on npm as the google-closure-compiler but only versions newer than we used are published and they don't work with ng-closure-compiler so - instead - both were checked in to the repository. Fixes #16268 Fixes #14961 Ref yarnpkg/yarn#1483 2017-12-27 19:16:46 +01:00			`"jquery": "3.2.1",`
			`"jquery-2.1": "npm:jquery@2.1.4",`
			`"jquery-2.2": "npm:jquery@2.2.4",`
chore(node): update karma to 2.0.0 Also reduce karma log level on Travis to INFO. Before, the log level was DEBUG, but it seems that prior to karma 2.0.0, the debug messages were not outoput on Karma, so this simply restores the status quo (and prevents cluttering the log). 2018-01-05 22:05:15 +01:00			`"karma": "^2.0.0",`
chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966 2017-05-06 17:50:42 +02:00			`"karma-browserstack-launcher": "^1.2.0",`
			`"karma-chrome-launcher": "^2.1.1",`
chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407 2018-01-15 13:07:45 +01:00			`"karma-edge-launcher": "^0.4.2",`
chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966 2017-05-06 17:50:42 +02:00			`"karma-firefox-launcher": "^1.0.1",`
chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407 2018-01-15 13:07:45 +01:00			`"karma-ie-launcher": "^1.0.0",`
chore(*): update all Karma-related packages except Karma The updated karma-chrome-launcher adds support for ChromeHeadless & ChromeCanaryHeadless launchers; test with: karma start karma-jqlite.conf.js --browsers=ChromeCanaryHeadless The updated karma-firefox-launcher disables multi-process which may increase stability on Jenkins. Closes #15966 2017-05-06 17:50:42 +02:00			`"karma-jasmine": "^1.1.0",`
			`"karma-junit-reporter": "^1.2.0",`
chore(node): add karma launchers for Edge, IE, and Safari That makes it easier to run the tests with these browsers locally. Closes #16407 2018-01-15 13:07:45 +01:00			`"karma-safari-launcher": "^1.0.0",`
chore(node): update karma-sauce-launcher Related to #14961 Closes #16281 2017-10-16 11:51:00 +02:00			`"karma-sauce-launcher": "^1.2.0",`
chore(package.json): update Karma & BrowserStack-related packages 2016-08-05 20:24:42 +02:00			`"karma-script-launcher": "^1.0.0",`
chore(travis): use "karma-spec-reporter" dots reporter creates lots of empty space that makes it tedious to scroll through the logs. "Spec" is configured to only report on failures. 2017-06-10 23:36:38 +02:00			`"karma-spec-reporter": "^0.0.31",`
chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt. 2016-07-20 00:54:17 +02:00			`"load-grunt-tasks": "^3.5.0",`
chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571 2014-10-11 21:58:38 +02:00			`"lodash": "~2.4.1",`
chore(npm): use require.resolve when possible to avoid hard coded module paths 2015-11-16 16:26:49 -08:00			`"log4js": "^0.6.27",`
chore(docs): don't use bower for docs dependencies 2016-12-01 13:26:51 +00:00			`"lunr": "^0.7.2",`
chore(doc-gen): new docs chore(doc-gen): implement dgeni 2014-02-12 22:47:42 +00:00			`"marked": "~0.3.0",`
chore(clean-shrinkwrap): add a utility to clean up the shrinkwrap file This is to deal with https://github.com/npm/npm/issues/3581 See the previous commit for more info. Closes #6672 2014-03-13 18:30:17 +00:00			`"node-html-encoder": "0.0.2",`
chore(utils): install npm-run to simplify scripts 2016-11-28 11:19:59 +00:00			`"npm-run": "^4.1.0",`
chore(docs): don't use bower for docs dependencies 2016-12-01 13:26:51 +00:00			`"open-sans-fontface": "^1.4.0",`
chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571 2014-10-11 21:58:38 +02:00			`"promises-aplus-tests": "~2.1.0",`
chore(*): update protractor Update protractor to latest 5.1.2 to make it work with Chrome 58 on Jenkins. This protractor version is not compatible with FF 53 and directConnect, but this should be irrelevant as Travis does not use directConnect and on Jenkins we don't test FF. Closes #15991 2017-05-17 09:22:34 +02:00			`"protractor": "^5.1.2",`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"q": "~1.0.0",`
			`"q-io": "^1.10.9",`
chore(perf): add event delegation benchmark 2014-07-31 06:26:10 -07:00			`"qq": "^0.3.5",`
chore(npm): update npm dependencies Some of previous dependencies versions (e.g. Karma) didn't work with Node 0.11.14, see: https://github.com/karma-runner/karma/pull/1182 The only dependencies not updated in this commit are: 1. grunt-jscs-checker: its rules have changed a lot so it will require more work to use the newer version 2. gulp-jshint: the update breaks docs linting, it requires investigation Closes #9571 2014-10-11 21:58:38 +02:00			`"rewire": "~2.1.0",`
feat(ngParseExt): New ngParseExt module New ngParseExt module Including this module into an application will extend $parse to allow identifiers following ES6 identifiers 2015-09-20 21:29:59 +02:00			`"sax": "^1.1.1",`
chore(npm): use require.resolve when possible to avoid hard coded module paths 2015-11-16 16:26:49 -08:00			`"selenium-webdriver": "^2.53.1",`
chore(node): update semver Closes #16396 2018-01-09 12:57:45 +01:00			`"semver": "^5.4.1",`
chore(package.json): add grunt-cli to devDependencies, update grunt-* packages The Travis build.sh script has to be updated as the previous way of specifying parameters to the code run in Grunt tasks stopped working with the newest Grunt. 2016-07-20 00:54:17 +02:00			`"serve-favicon": "^2.3.0",`
			`"serve-index": "^1.8.0",`
			`"serve-static": "^1.11.1",`
chore(package.json): update to latest version of shelljs 2016-11-11 19:47:28 +00:00			`"shelljs": "^0.7.5",`
chore(package.json): tidy up dependencies Sorted dependencies into alphabetic order. If we can keep them like this it will be much easier to keep track of version changes. Updated bower and gulp to newer versions. 2014-09-08 09:50:47 +01:00			`"sorted-object": "^1.0.0",`
chore(*): switch from JSHint/JSCS to ESLint Thanks to @narretz for help in fixing style violations and to @gkalpak for a very extensive review. Closes #14952 2016-07-20 15:45:04 +02:00			`"stringmap": "^0.2.2"`
chore(NPM): Add license info 2013-03-27 00:12:45 -07:00			`},`
chore(package.json): add commitizen, adapter and npm script Closes #13194 2015-10-28 12:38:21 -04:00			`"dependencies": {},`
chore(travis): add commitplease validation to ci-checks This will provide feedback to contributors without getting in the way of writing invalid commit messages locally. The git hook integration is turned off. Committers who push directly to the repo can be expected to use correct commit messages ;) Most changes go through PRs anyway. Note that "Merge commit" messages and everything starting with "WIP" is always allowed by commitplease. Follow issue https://github.com/jzaefferer/commitplease/issues/101 for more info. Related to #14888 Closes #16097 2017-07-12 12:02:18 +02:00			`"commitplease": {`
			`"style": "angular",`
			`"nohook": true`
			`},`
chore(package.json): add commitizen, adapter and npm script Closes #13194 2015-10-28 12:38:21 -04:00			`"config": {`
			`"commitizen": {`
			`"path": "node_modules/cz-conventional-changelog"`
			`}`
			`}`
chore(node): update karma-sauce-launcher Related to #14961 Closes #16281 2017-10-16 11:51:00 +02:00			`}`