iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/package.json

89 lines
2.5 KiB
JSON
Raw Normal View History

build - refactor
2014-09-18 17:56:38 -04:00
{
chore(package.json): remove typings bundles This was used for , but now that our typings are laid out in the node_module, users should no longer need that. Also fix the project name in root package.json. There is a risk that someone runs npm publish in this directory, which will create a new version of angular 1, and contain a scary source tree. So this package.json may as well have a name that doesn't exist on npm, and if we did publish by accident, it would be a package name that matches the contents.
2015-10-15 12:57:29 -04:00
"name": "angular-srcs",
chore(release): cut the 2.2.0-beta.0 release
2016-10-27 12:28:07 -04:00
"version": "2.2.0-beta.1",
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"private": true,
chore(doc-gen): improve github links to point to the correct tagged URL Closes #1994
2015-05-19 17:29:34 -04:00
"branchPattern": "2.0.*",
feat(build): add npm publish script Also fixes gulpfile: - `runSequence` needs to be called with `done` callback - `es5build` should only run when the task executes…
2015-02-10 18:18:16 -05:00
"description": "Angular 2 - a web framework for modern web apps",
"homepage": "https://github.com/angular/angular",
"bugs": "https://github.com/angular/angular/issues",
doc(*): change package.json license field to MIT Align the package.json license with the LICENSE file from the repo Closes #6432
2016-01-12 11:36:43 -05:00
"license": "MIT",
chore(package.json): add range of supported node versions as engines Closes #5535
2015-12-01 17:09:31 -05:00
"engines": {
chore(node): allow current node version node current is 6.6.0 see https://github.com/nodejs/LTS#lts_schedule
2016-09-19 14:37:44 -04:00
"node": ">= 5.4.1 < 7"
chore(package.json): add range of supported node versions as engines Closes #5535
2015-12-01 17:09:31 -05:00
},
chore(package.json): npm No repository field. npm install yields a warning ```bash npm WARN package.json angular@0.0.0 No repository field. ``` also include `"bugs": "https://github.com/angular/angular/issues"`
2015-01-24 13:50:18 -05:00
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git"
},
build - refactor
2014-09-18 17:56:38 -04:00
"scripts": {
build: fix some issues on Windows platforms Closes #9450
2016-06-20 18:25:55 -04:00
"postinstall": "node tools/npm/copy-npm-shrinkwrap && webdriver-manager update"
build - refactor
2014-09-18 17:56:38 -04:00
},
"dependencies": {
chore(dependencies): switch from es6-shim to core-js (#10884)
2016-08-25 20:28:36 -04:00
"core-js": "^2.4.1",
Bump reflect-metadata to 0.1.3 Closes #7663
2016-03-18 09:01:49 -04:00
"reflect-metadata": "^0.1.3",
build(npm): update to rxjs@5.0.0-beta.12 Fixes #11300
2016-09-12 15:05:00 -04:00
"rxjs": "5.0.0-beta.12",
chore(zone.js): update to 0.6.25 (#11725)
2016-09-20 17:55:07 -04:00
"zone.js": "^0.6.25"
chore: use load-plugins to make gulpfile shorter
2014-11-11 11:37:19 -05:00
},
"devDependencies": {
build: remove dependency on tsd and use @types/* instead
2016-05-25 18:37:40 -04:00
"@types/angularjs": "^1.5.13-alpha",
"@types/fs-extra": "0.0.22-alpha",
"@types/hammerjs": "^2.0.22-alpha",
"@types/jasmine": "^2.2.22-alpha",
"@types/node": "^4.0.22-alpha",
"@types/protractor": "^1.5.11-alpha",
"@types/selenium-webdriver": "^2.44.20-alpha",
fix(angular1-router): add support for using the component helper In Angular 1.5 there is a new helper method for creating component directives. See https://docs.angularjs.org/guide/component for more information about components. These kind of directives only match the `E` element form and the previously component router only created HTML that matched directives that matched the `A` attribute form. This commit changes the `<ng-outlet>` directive so that it generates custom HTML elements rather divs with custom attributes to trigger the relevant component to appear in the DOM. Going forward, Angular 1.5 users are encouraged to create their router components using the following style: ``` myModule.componnet('component-name', { // component definition object }); ``` Closes angular/angular.js#13860 Closes #6076 Closes #5278 BREAKING CHANGE: The component router now creates custom element HTML rather than custom attribute HTML, in order to create a new component. So rather than ```html <div custom-component></div> ``` it now creates ```html <custom-component></custom-component> ``` If you defined you router components using the `directive()` helper and specified the `restrict` properties such that element matching was not allowed, e.g. `restrict: 'A'` then these components will no longer be instantiated by the component router and the outlet will be empty. The fix is to include `E` in the `restrict` property. `restrict: 'EA'` Note that this does not affect directives that did not specify the `restrict` property as the default for this property is already `EA`.
2016-01-31 10:35:23 -05:00
"angular": "^1.5.0",
"angular-animate": "^1.5.0",
"angular-mocks": "^1.5.0",
Feat(WebWorker): Add WebWorker Image Filter Demo
2015-07-31 13:33:22 -04:00
"base64-js": "^0.0.8",
chore(docs): initial dgeni docs generation Closes #261
2014-12-04 09:02:03 -05:00
"bower": "^1.3.12",
build(browserstack): add npm dependencies
2015-10-27 10:52:08 -04:00
"browserstacktunnel-wrapper": "^1.4.2",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"chokidar": "^1.1.0",
feat: upgrade clang-format to 1.0.32.
2015-10-20 05:10:31 -04:00
"clang-format": "^1.0.32",
fix(i18n): update NgLocalLocalization (#10771) ref https://github.com/papandreou/node-cldr/issues/31
2016-08-13 08:43:36 -04:00
"cldr": "^3.5.2",
build(npm): update conventional-changelog dependency Fixes #5672
2016-06-23 18:54:45 -04:00
"conventional-changelog": "^1.1.0",
build(serve): added cors support for the js.server task Added and used the cors middleware: - add the module as a dev depedency in the package.json file - require the module in the jsserve.js file - add the module in the middleware list Closes #7273 Closes #7274
2016-02-25 03:28:01 -05:00
"cors": "^2.7.1",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"firefox-profile": "^0.3.4",
build(npm): update to fs-extra@0.26.3
2016-01-02 23:05:56 -05:00
"fs-extra": "^0.26.3",
build(npm): update fsevents to 1.0.14 (#11686) fixes #11685
2016-09-18 19:04:46 -04:00
"fsevents": "^1.0.14",
chore: move npm's dev dependencies to the devDependencies section
2015-01-02 05:58:34 -05:00
"glob": "^4.0.6",
chore: use load-plugins to make gulpfile shorter
2014-11-11 11:37:19 -05:00
"gulp": "^3.8.8",
build(npm): bump gulp-clang-format to ^1.0.23 This is due to https://github.com/angular/gulp-clang-format/issues/7
2015-11-04 22:06:03 -05:00
"gulp-clang-format": "^1.0.23",
build(npm): update to gulp-connect@2.3.1
2016-01-03 11:44:31 -05:00
"gulp-connect": "^2.3.1",
build(npm): update conventional-changelog dependency Fixes #5672
2016-06-23 18:54:45 -04:00
"gulp-conventional-changelog": "^1.1.0",
fix(packages): use ES modules for primary build (#11120)
2016-08-30 21:07:40 -04:00
"gulp-tslint": "^6.1.1",
chore: add incremental-dom as dev dependency
2016-09-01 13:28:17 -04:00
"incremental-dom": "^0.4.1",
build(npm): roll back jasmine 2.5 upgrade due to console reporter issues (#11573) 2.5.1 no longer prints dots in the './test.sh node' mode
2016-09-13 16:32:58 -04:00
"jasmine": "^2.4.1",
Fix benchpress for newest protractor and selenium (#11451) * chore: update protractor and selenium-webdriver packages As `karma-jasmine` has a peer dependency on `jasmine-core@2.3`, but `jasmine` and `protractor` are using `jasmine-core@2.4` we need to add `jasmine-core@2.3` explicitly. Previously, the peer dependency was satisfied by accident because npm deduped the dependency for `jasmine-core@2.3` as top level dependency. Note that the shrink-wrap files changes quite a bit because of the deduping mechanism of npm. * fix(benchpress): make it work with latest protractor and seleniuv-webdriver * fix(e2e_tests): make them work with latest protractor
2016-09-09 13:37:47 -04:00
"jasmine-core": "^2.3.4",
chore(shrinkwrap): add shrinkwrap for firefox-profile/jpm and update package.json for benchpress closes #2264
2015-06-01 16:40:31 -04:00
"jpm": "1.0.0",
upgrade karma to v0.13.20 due to 'invalid characters in the headers on Node 5.6.0'(#1884) issue Closes #7885
2016-04-02 10:32:31 -04:00
"karma": "^0.13.20",
build(npm): update to karma-browserstack-launcher@0.1.9
2016-01-12 01:58:59 -05:00
"karma-browserstack-launcher": "^0.1.9",
build(npm): update chokidar and karma* dependencies These dependencies required upgrade in order for us to run on Node v4.x chokidar 1.0.1 -> 1.1.0 karma 0.12.23 -> 0.13.10 karma-chorome-launcher 0.1.8 -> 0.2.0 karma-cli 0.0.4 -> 0.1.0 karma-dart 0.2.8 -> 0.3.0 karma-sauce-launcher 0.2.11 -> 0.2.14
2015-09-25 18:26:31 -04:00
"karma-chrome-launcher": "^0.2.0",
chore(package.json): update karma-jasmine Closes #4116
2015-09-10 12:32:28 -04:00
"karma-jasmine": "^0.3.6",
build(npm): upgrade to karma-sauce-launcher@0.3.0
2016-01-02 03:39:11 -05:00
"karma-sauce-launcher": "^0.3.0",
fix(build): fix source maps Closes #5444
2015-11-23 17:58:18 -05:00
"karma-sourcemap-loader": "^0.3.6",
build(npm): freeze madge at 0.5.0 due to #5022
2015-11-03 23:23:26 -05:00
"madge": "0.5.0",
build(npm): update to minimatch@3.0.0
2016-01-03 13:01:43 -05:00
"minimatch": "^3.0.0",
build(npm): update to minimist@1.2.0
2016-01-02 22:56:03 -05:00
"minimist": "^1.2.0",
build(npm): update fsevents to 1.0.14 (#11686) fixes #11685
2016-09-18 19:04:46 -04:00
"nan": "^2.4.0",
fix(package.json): move some deps into dev deps. Closes #2448
2015-07-09 14:26:33 -04:00
"node-uuid": "1.4.x",
feat(Parse5): update to the latest version 2.2.1 fixes #6237
2016-09-26 14:01:12 -04:00
"parse5": "^2.2.1",
Fix benchpress for newest protractor and selenium (#11451) * chore: update protractor and selenium-webdriver packages As `karma-jasmine` has a peer dependency on `jasmine-core@2.3`, but `jasmine` and `protractor` are using `jasmine-core@2.4` we need to add `jasmine-core@2.3` explicitly. Previously, the peer dependency was satisfied by accident because npm deduped the dependency for `jasmine-core@2.3` as top level dependency. Note that the shrink-wrap files changes quite a bit because of the deduping mechanism of npm. * fix(benchpress): make it work with latest protractor and seleniuv-webdriver * fix(e2e_tests): make them work with latest protractor
2016-09-09 13:37:47 -04:00
"protractor": "^4.0.5",
fix(benchmarks): update react and polymer benchmarks and get tree update numbers for all of the benchmarks as well. Closes #4709
2015-10-13 18:10:20 -04:00
"react": "^0.14.0",
chore(package.json): add rewire devDependency
2015-05-13 22:58:40 -04:00
"rewire": "^2.3.3",
build: update to rollup@0.26.3 and remove a hack from the build
2016-05-20 13:24:05 -04:00
"rollup": "^0.26.3",
Fix benchpress for newest protractor and selenium (#11451) * chore: update protractor and selenium-webdriver packages As `karma-jasmine` has a peer dependency on `jasmine-core@2.3`, but `jasmine` and `protractor` are using `jasmine-core@2.4` we need to add `jasmine-core@2.3` explicitly. Previously, the peer dependency was satisfied by accident because npm deduped the dependency for `jasmine-core@2.3` as top level dependency. Note that the shrink-wrap files changes quite a bit because of the deduping mechanism of npm. * fix(benchpress): make it work with latest protractor and seleniuv-webdriver * fix(e2e_tests): make them work with latest protractor
2016-09-09 13:37:47 -04:00
"selenium-webdriver": "^2.53.3",
build(npm): update to semver@5.1.0
2016-01-03 12:58:55 -05:00
"semver": "^5.1.0",
chore(sourcemaps): add e2e test
2015-02-11 17:54:59 -05:00
"source-map": "^0.3.0",
build(npm): remove obsolete npm dependencies I also removed an obsolete bundling script which depended on systemjs-builder that I removed.
2016-09-02 15:46:49 -04:00
"source-map-support": "^0.4.2",
build(npm): lock systemjs at 0.18.10 due to regressions in future versions otherwise in dist/js/dev/es5/benchmarks/src/naive_infinite_scroll/index.html defaultExtension: 'js' is ignored for angular2/src/testing/benchmark_util which results in test failures. We'll need to investigate this. Maybe upgrading to 0.19.x will make this issue go away...
2015-11-05 02:48:21 -05:00
"systemjs": "0.18.10",
build(npm): upgrade ts-api-guardian to v0.1.4 Closes #9642
2016-06-27 13:02:02 -04:00
"ts-api-guardian": "0.1.4",
fix(packages): use ES modules for primary build (#11120)
2016-08-30 21:07:40 -04:00
"tsickle": "^0.1.7",
"tslint": "^3.15.0-dev.0",
chore: update to typescript@2.0.2 - the currect 2.0 rc
2016-08-30 17:42:33 -04:00
"typescript": "^2.0.2",
build(analytics): add basic build-analytics to the project This is pretty experimental, but the goal is to track the performance of our build over time so that we can more easily track perf regressions. Currently it's integrated only with gulp tasks, but I'd like to expand it to tracking travis jobs, protractor/benchpress test runs, npm installs, etc. No PII is being collected. And the data is collected via a Google Analytics property owned by the Angular team account. Closes #4672
2015-10-11 05:23:05 -04:00
"universal-analytics": "^0.3.9",
chore(lint): add vrsource tslint rules dependency
2016-10-27 14:46:50 -04:00
"vrsource-tslint-rules": "^0.14.1",
feat(bundles): publish UMD bundles Closes #5223
2015-11-16 09:59:05 -05:00
"webpack": "^1.12.6",
build(npm): update to yargs@3.31.0
2016-01-03 12:29:02 -05:00
"yargs": "^3.31.0"
chore: karma with JS, Dart Note: karma with dart is still not working because of how `karma-dart` loads `package:…` dependencies. Usage: ``` karma start karma-js.conf.js karma start karma-dart.conf.js ``` Make sure to set `DARTIUM_BIN` env variable. Refactors `js2dart`: - live outside of the traceur module (`tools/js2dart/index.js`) so it can be reused by gulp and karma - automatically build the sources in memory, so that `js2dart` can be used without running `gulp build` first - provide a way to specify the moduleName of a compilation run independently of the input filename. This helps error messages and source maps (not yet enabled) to report the correct file name Changes project setup: - add module `test_lib` that contains the primitives for tests (e.g. `describe`, `it`, …) - clean up some sources that had errors in them - module names in transpiled js and dart files don’t contain `lib`, `test` nor `src` any more (e.g. `di/di`).
2014-09-25 17:04:46 -04:00
}
build - refactor
2014-09-18 17:56:38 -04:00
}