angular-cn/packages/animations/package.json

{
  "name": "@angular/animations",
  "version": "0.0.0-PLACEHOLDER",
  "description": "Angular - animations integration with web-animations",
  "author": "angular",
  "license": "MIT",
  "engines": {
    "node": "^12.14.1 || ^14.0.0"
  },
  "dependencies": {
    "tslib": "^2.1.0"
  },
  "peerDependencies": {
    "@angular/core": "0.0.0-PLACEHOLDER"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/angular/angular.git",
    "directory": "packages/animations"
  },
  "ng-update": {
    "packageGroup": "NG_UPDATE_PACKAGE_GROUP"
  },
  "sideEffects": false,
  "publishConfig":{
    "registry":"https://wombat-dressing-room.appspot.com"
  }
}
refactor(animations): support browser animation rendering (#14578) 2017-02-22 18:14:49 -05:00			`{`
			`"name": "@angular/animations",`
			`"version": "0.0.0-PLACEHOLDER",`
refactor(animations): fix typo (#24210) closes #22459 PR Close #24210 2018-02-26 12:58:00 -05:00			`"description": "Angular - animations integration with web-animations",`
refactor(animations): support browser animation rendering (#14578) 2017-02-22 18:14:49 -05:00			`"author": "angular",`
			`"license": "MIT",`
feat(animations): 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. PR Close #41544 2021-04-12 15:12:14 -04:00			`"engines": {`
fix(animations): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 2021-04-26 14:46:42 -04:00			`"node": "^12.14.1 \|\| ^14.0.0"`
feat(animations): 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. PR Close #41544 2021-04-12 15:12:14 -04:00			`},`
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 08:35:37 -04: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 15:10:32 -04: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 08:35:37 -04:00			`},`
refactor(animations): support browser animation rendering (#14578) 2017-02-22 18:14:49 -05:00			`"peerDependencies": {`
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 08:35:37 -04:00			`"@angular/core": "0.0.0-PLACEHOLDER"`
refactor(animations): support browser animation rendering (#14578) 2017-02-22 18:14:49 -05:00			`},`
			`"repository": {`
			`"type": "git",`
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544 2018-12-07 06:12:59 -05:00			`"url": "https://github.com/angular/angular.git",`
			`"directory": "packages/animations"`
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 18:04:35 -05:00			`},`
			`"ng-update": {`
			`"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 21:30:18 -04:00			`},`
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495) This reverts commit 26849ca99dcafc45fb8cb0e97af7aeb85ea11852. PR Close #37495 2020-06-08 21:07:39 -04:00			`"sideEffects": false,`
			`"publishConfig":{`
			`"registry":"https://wombat-dressing-room.appspot.com"`
			`}`
refactor(animations): support browser animation rendering (#14578) 2017-02-22 18:14:49 -05:00			`}`