honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/core/package.json

28 lines
634 B
JSON
Raw Normal View History

repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
{
"name": "@angular/core",
chore(package.json): make the packages installable
2016-05-27 19:17:16 -04:00
"version": "0.0.0-PLACEHOLDER",
docs: update descriptions in package.jsons
2016-09-14 19:44:39 -04:00
"description": "Angular - the core framework",
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"author": "angular",
"license": "MIT",
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": {
针对新的版本提交没有提交的代码
2021-04-03 09:52:53 -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
},
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"peerDependencies": {
feat: update rxjs peerDependencies minimum requirment to 6.5.3 (#32812) PR Close #32812
2019-10-01 13:59:49 -04:00
"rxjs": "^6.5.3",
针对新的版本提交没有提交的代码
2021-04-03 09:52:53 -04:00
"zone.js": "~0.11.4"
adds 'repository' metadata to npm modules (#8649)
2016-05-18 02:17:15 -04: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/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 18:04:35 -05: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-17 19:52:34 -05: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 18:04:35 -05: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 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"
}
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-17 19:52:34 -05:00
}