Hopiu/angular.js
1
0
Fork 0
mirror of https://github.com/Hopiu/angular.js.git synced 2026-03-16 23:30:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular.js/package.json

57 lines
1.6 KiB
JSON
Raw Normal View History

chore(package.json): add simple package.json with npm dependencies
2012-05-23 06:39:07 +00:00
{
chore(package.json): fix name to work with latest NPM
2013-07-14 00:20:56 +00:00
"name": "angularjs",
chore(release): start v1.2.12 (1.2.12)
2014-02-03 17:41:17 +00:00
"version": "1.2.12-snapshot",
chore(release): update cdn version
2014-01-25 03:27:18 +00:00
"cdnVersion": "1.2.10",
chore(release): start v1.2.12 (1.2.12)
2014-02-03 17:41:17 +00:00
"codename": "cauliflower-eradication",
fix(package.json): add a repository field The `npm install` command complains about the missing repository field. Closes #3674
2013-08-20 14:49:43 +00:00
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.js.git"
},
chore(package.json): use `devDependencies` instead of `dependencies`
2013-05-18 15:41:27 +00:00
"devDependencies": {
chore(build): add jscs code style check to our build Closes #6062
2014-01-30 18:51:10 +00:00
"grunt": "~0.4.2",
fix(package.json): use full version numbers when interpolating When using less than 3 numbers in npm package version together with tilde interpolation, it lets major version upgrades, e.g. "~0.10" means at least 0.10 and less than 1.0; this pattern would match e.g. 0.11, 0.12 etc. Besides, some package.json dependencies were upgraded.
2013-08-21 09:56:21 +00:00
"bower": "~1.2.2",
chore(build): automate cutting a release, publishing to bower and to code.angular.js
2013-12-13 20:49:42 +00:00
"grunt-bump": "~0.0.13",
fix(package.json): use full version numbers when interpolating When using less than 3 numbers in npm package version together with tilde interpolation, it lets major version upgrades, e.g. "~0.10" means at least 0.10 and less than 1.0; this pattern would match e.g. 0.11, 0.12 etc. Besides, some package.json dependencies were upgraded.
2013-08-21 09:56:21 +00:00
"grunt-contrib-clean": "~0.5.0",
"grunt-contrib-compress": "~0.5.2",
chore(package.json): update npm packages Some of node dependencies have much newer versions; one of them is Lo-Dash that has recently released the 2.0.0 version bringing in new useful methods.
2013-09-24 17:43:25 +00:00
"grunt-contrib-connect": "~0.5.0",
fix(package.json): use full version numbers when interpolating When using less than 3 numbers in npm package version together with tilde interpolation, it lets major version upgrades, e.g. "~0.10" means at least 0.10 and less than 1.0; this pattern would match e.g. 0.11, 0.12 etc. Besides, some package.json dependencies were upgraded.
2013-08-21 09:56:21 +00:00
"grunt-contrib-copy": "~0.4.1",
"jasmine-node": "~1.11.0",
chore($ngLocale): refactor i18n closure slurper logic and parse extended datetime symbols
2013-03-08 23:37:56 +00:00
"q": "~0.9.2",
docs: use q-io instead of deprecated q-fs This recursive process.nextTick error[1] was probably coming from q-fs, which is not actively maintained. This updates to q-io/fs instead. [1]: https://travis-ci.org/angular/angular.js/jobs/15391590
2013-12-13 19:59:23 +00:00
"q-io": "~1.10.6",
fix(package.json): use full version numbers when interpolating When using less than 3 numbers in npm package version together with tilde interpolation, it lets major version upgrades, e.g. "~0.10" means at least 0.10 and less than 1.0; this pattern would match e.g. 0.11, 0.12 etc. Besides, some package.json dependencies were upgraded.
2013-08-21 09:56:21 +00:00
"qq": "~0.3.5",
chore(package.json): update npm packages Some of node dependencies have much newer versions; one of them is Lo-Dash that has recently released the 2.0.0 version bringing in new useful methods.
2013-09-24 17:43:25 +00:00
"shelljs": "~0.2.6",
chore: strict deps Karma and plugins So that we have a better control when updating Karma.
2014-01-06 19:27:19 +00:00
"karma": "0.11.12",
"karma-jasmine": "0.1.5",
"karma-chrome-launcher": "0.1.2",
"karma-firefox-launcher": "0.1.3",
"karma-ng-scenario": "0.1.0",
"karma-junit-reporter": "0.2.1",
"karma-sauce-launcher": "0.2.0",
"karma-script-launcher": "0.1.0",
"karma-browserstack-launcher": "0.0.7",
test(docs): convert example end to end doc tests from scenario runner to protractor Thanks to jeffbcross, petebacondarwin, btford, jdeboer, tbosch for contributions! Closes #6023
2014-01-12 00:59:15 +00:00
"protractor": "~0.17.0",
fix(package.json): use full version numbers when interpolating When using less than 3 numbers in npm package version together with tilde interpolation, it lets major version upgrades, e.g. "~0.10" means at least 0.10 and less than 1.0; this pattern would match e.g. 0.11, 0.12 etc. Besides, some package.json dependencies were upgraded.
2013-08-21 09:56:21 +00:00
"yaml-js": "~0.0.8",
chore(package.json): revert to marked@0.2.9 to fix CI builds The marked npm library brought in a breaking change at 0.2.10. This commit ensures that we get exactly the version we want. Closes #4822
2013-11-07 17:08:32 +00:00
"marked": "0.2.9",
chore(doc_gen): add task to run doc-gen specs
2013-06-23 21:27:18 +00:00
"rewire": "1.1.3",
chore: use temporary version of grunt-jasmine-node This should be reverted once https://github.com/jasmine-contrib/grunt-jasmine-node/pull/33 gets merged in the upstream repo. It fixes the problem where Grunt does not fail the build, even though there are failures. See https://travis-ci.org/angular/angular.js/builds/14329011#L2366
2013-11-21 20:12:23 +00:00
"grunt-jasmine-node": "git://github.com/vojtajina/grunt-jasmine-node.git#fix-grunt-exit-code",
chore: switch back to npm grunt-parallel The patch has been released so we don't need to rely on github branch anymore.
2013-08-28 19:08:59 +00:00
"grunt-parallel": "~0.3.1",
chore(build): add check for merge conflicts, ddescribe, and iit
2013-07-03 18:10:23 +00:00
"grunt-ddescribe-iit": "~0.0.1",
chore(tests): add Promises/A+ Test Suite to the build Closes #3693
2013-08-21 23:17:07 +00:00
"grunt-merge-conflict": "~0.0.1",
"promises-aplus-tests": "~1.3.2",
chore(package.json): update npm packages Some of node dependencies have much newer versions; one of them is Lo-Dash that has recently released the 2.0.0 version bringing in new useful methods.
2013-09-24 17:43:25 +00:00
"grunt-shell": "~0.4.0",
chore(release): add script for comparing master and stable branches
2013-08-10 00:26:07 +00:00
"semver": "~2.1.0",
chore(travis): let's give BrowserStack a try Switch the build to use BrowserStack instead of SauceLabs. This also adds IE11 to our build.
2013-11-20 00:50:23 +00:00
"lodash": "~2.1.0",
chore(build): add jscs code style check to our build Closes #6062
2014-01-30 18:51:10 +00:00
"browserstacktunnel-wrapper": "~1.1.1",
"grunt-jscs-checker": "~0.3.2"
chore(NPM): Add license info
2013-03-27 07:12:45 +00:00
},
"licenses": [
{
"type": "MIT",
"url": "https://github.com/angular/angular.js/blob/master/LICENSE"
}
chore(grunt): add jshint tasks
2013-10-21 08:06:53 +00:00
],
"dependencies": {
chore(grunt): update to latest jshint task Upgrade JSHint task from ~0.6.4 to ~0.7.2. Two useful changes: ability to set jshintrc option to use jshint's native ability for finding .jshintrc files relative to the linted files and update jshint to 2.3.0. Closes #5143
2013-11-26 21:26:10 +00:00
"grunt-contrib-jshint": "~0.7.2"
chore(grunt): add jshint tasks
2013-10-21 08:06:53 +00:00
}
chore(package.json): add simple package.json with npm dependencies
2012-05-23 06:39:07 +00:00
}
Reference in a new issue Copy permalink