288851c41e
"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: 2e8b12a4ef/docs/specifications/update.md
PR Close #22482
26 lines
566 B
JSON
26 lines
566 B
JSON
{
|
|
"name": "@angular/core",
|
|
"version": "0.0.0-PLACEHOLDER",
|
|
"description": "Angular - the core framework",
|
|
"main": "./bundles/core.umd.js",
|
|
"module": "./esm5/core.js",
|
|
"es2015": "./esm2015/core.js",
|
|
"typings": "./core.d.ts",
|
|
"author": "angular",
|
|
"license": "MIT",
|
|
"dependencies": {
|
|
"tslib": "^1.7.1"
|
|
},
|
|
"peerDependencies": {
|
|
"rxjs": "^5.5.0",
|
|
"zone.js": "^0.8.4"
|
|
},
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/angular/angular.git"
|
|
},
|
|
"ng-update": {
|
|
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
|
|
}
|
|
}
|