Angular 8 is still in beta. With Angular 8.0.0-beta.11 new features are ready for testing. There is also a Breaking Change for Bazel.
The release cycle of Angular provides for a new major release every six months. That works better, but sometimes not so good. At Angular 7 the release came on time in October. Thus, Angular 8 would have to follow in April or May 2019. Until then, it continues first with minor releases of Angular 7 and then the beta versions of Angular 8.
4th April 2019
With Angular 8.0.0-beta.11, the next beta is ready for the upcoming major release of Angular. As announced in February, Angular 8 will move into the release candidate phase later this month. For the time being, however, there are still new features and breaking changes to the version. New features in the now released Beta 11 are four features, one of which could be omitted as part of the RC phase, if it should make the migration too difficult . The change affects @ angular / http, which should be hidden in v8 altogether in order to be able to skip certain steps in the package. The package has now been removed from @ angular / platform-server.
Another feature in the new beta release concerns logging. It is now possible to filter redundant log messages with the CLI or via plug-in and to create a configuration for the output of the messages. An “AbstractType” interface is also available for the core, which generates types that are used for classes in get() functions of Injectors and TestBed. So far, however, only the interface has been implemented and the corresponding type is not used, so it is not a breaking change, as can be seen in the pull request . The fourth and last new feature is a new update schematic called “template-var-assignment”. The schematic should issue a warning when template variables are assigned to values.
Also for Bazel there is another change. This is the breaking change for all users who already work with the experimental feature. Since @ bazel / typescript is now a peer dependency of @ angular / bazel, it must be added to package.json.