angular-cn/packages/upgrade
Hans Larsen 288851c41e 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: 2e8b12a4ef/docs/specifications/update.md

PR Close #22482
2018-02-28 14:57:53 -08:00
..
src fix(upgrade): correctly destroy nested downgraded component (#22400) 2018-02-27 18:41:02 -08:00
static build: move repeated tsconfig attributes to a macro (#20964) 2018-01-10 12:30:19 -08:00
test fix(upgrade): correctly destroy nested downgraded component (#22400) 2018-02-27 18:41:02 -08:00
BUILD.bazel refactor(bazel): convert most ts_library to ng_module (#22176) 2018-02-15 14:08:53 -08:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
package.json release: add ng update package group metadata to angular (#22482) 2018-02-28 14:57:53 -08:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
rollup.config.js refactor: make all rollup config ES5 compatible (#20028) 2017-10-30 23:09:17 -04:00
tsconfig-build.json build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -07:00