angular-cn/packages/platform-browser
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
..
animations fix(animations): only use the WA-polyfill alongside AnimationBuilder (#22143) 2018-02-22 16:07:53 -08:00
src feat(platform-browser): do not throw error when Hammer.js not loaded (#22257) 2018-02-18 13:29:14 -08:00
test test(platform-browser): remove stray `debugger` statement (#22167) 2018-02-25 10:06:14 -08:00
testing refactor(bazel): convert most ts_library to ng_module (#22176) 2018-02-15 14:08:53 -08:00
BUILD.bazel build: update some ts_library rules to ng_module (#22005) 2018-02-12 14:34:59 -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 fix: don’t use the global `ng` at all with closure enhanced optimizations 2017-09-27 10:09:56 -07:00