angular-cn/packages/core/package.json

{
  "name": "@angular/core",
  "version": "0.0.0-PLACEHOLDER",
  "description": "Angular - the core framework",
  "author": "angular",
  "license": "MIT",
  "engines": {
    "node": ">=12.14.1 <16.0.0"
  },
  "dependencies": {
    "tslib": "^2.1.0"
  },
  "peerDependencies": {
    "rxjs": "^6.5.3",
    "zone.js": "~0.11.4"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/angular/angular.git",
    "directory": "packages/core"
  },
  "ng-update": {
    "migrations": "./schematics/migrations.json",
    "packageGroup": "NG_UPDATE_PACKAGE_GROUP"
  },
  "sideEffects": false,
  "publishConfig": {
    "registry": "https://wombat-dressing-room.appspot.com"
  }
}
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`{`
			`"name": "@angular/core",`
chore(package.json): make the packages installable 2016-05-27 16:17:16 -07:00			`"version": "0.0.0-PLACEHOLDER",`
docs: update descriptions in package.jsons 2016-09-14 16:44:39 -07:00			`"description": "Angular - the core framework",`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`"author": "angular",`
			`"license": "MIT",`
feat(core): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. BREAKING CHANGE: Angular no longer maintains support for node v10 PR Close #41544 2021-04-12 12:08:28 -07:00			`"engines": {`
			`"node": ">=12.14.1 <16.0.0"`
			`},`
refactor: update to tslib 2.0 and move to direct dependencies (#37198) Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed. Reference: TOOL-1374 and TOOL-1375 Closes: #37188 PR Close #37198 2020-05-19 14:35:37 +02:00			`"dependencies": {`
feat(core): support TypeScript 4.2 (#41158) Updates the repo to TypeScript 4.2 and tslib 2.1.0. PR Close #41158 2021-03-16 20:10:32 +01:00			`"tslib": "^2.1.0"`
refactor: update to tslib 2.0 and move to direct dependencies (#37198) Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed. Reference: TOOL-1374 and TOOL-1375 Closes: #37188 PR Close #37198 2020-05-19 14:35:37 +02:00			`},`
repackaging: all the repackaging changes squashed 2016-04-28 17:50:03 -07:00			`"peerDependencies": {`
feat: update rxjs peerDependencies minimum requirment to 6.5.3 (#32812) PR Close #32812 2019-10-01 19:59:49 +02:00			`"rxjs": "^6.5.3",`
feat(core): drop support for zone.js 0.10.x (#40823) With this change we drop support for zone.js 0.10.x. This is needed because in version 12 the CLI will only work with `~0.11.4`. See angular/angular-cli#20034. BREAKING CHANGE: Minimum supported `zone.js` version is `0.11.4` PR Close #40823 2021-02-17 08:46:48 +01:00			`"zone.js": "~0.11.4"`
adds 'repository' metadata to npm modules (#8649) 2016-05-18 08:17:15 +02:00			`},`
			`"repository": {`
			`"type": "git",`
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544 2018-12-07 12:12:59 +01:00			`"url": "https://github.com/angular/angular.git",`
			`"directory": "packages/core"`
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482 2018-02-27 15:04:35 -08:00			`},`
			`"ng-update": {`
build: update zone.js to 0.9.0 (#28219) The API changes are due to enabling strict checks in TypeScript (via `strict: true`). The payload size changes in `polyfills.js` are due to more browser APIs being patched in recent versions (e.g. `fetch`, `customElement v1`). PR Close #28219 2019-01-18 09:52:34 +09:00			`"migrations": "./schematics/migrations.json",`
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482 2018-02-27 15:04:35 -08:00			`"packageGroup": "NG_UPDATE_PACKAGE_GROUP"`
feat: mark angular packages as side-effect free (#22785) This flag is picked up by webpack v4 and used for more agressive optimizations. Our code is already side-effect free, because that's what we needed for build-optimizer to work. PR Close #22785 2018-03-14 18:30:18 -07:00			`},`
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495) This reverts commit 26849ca99dcafc45fb8cb0e97af7aeb85ea11852. PR Close #37495 2020-06-08 19:07:39 -06:00			`"sideEffects": false,`
			`"publishConfig": {`
			`"registry": "https://wombat-dressing-room.appspot.com"`
			`}`
build: update zone.js to 0.9.0 (#28219) The API changes are due to enabling strict checks in TypeScript (via `strict: true`). The payload size changes in `polyfills.js` are due to more browser APIs being patched in recent versions (e.g. `fetch`, `customElement v1`). PR Close #28219 2019-01-18 09:52:34 +09:00			`}`