Angular 7.1 is here, Ivy is not and yet it’s already on with Angular 7.2 on: The second beta has some features for Bazel delivered, including the official Angular Schmematics for Bazel. However, there is also a breaking change in the release.
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.
Angular 7.x: The minor releases
Update from December 7, 2018
After the small first beta for Angular 7.2, the second is even bigger: With numerous bug fixes, some features and even a breaking change, the latest beta release of Angular is available for download. The theme of the new version is obvious: it’s about Bazel. Bazel is a build and test tool developed independently of Angular. The Angular team has been working on integrating the tool into Angular for a while, making it easy for Angular users to access. The Angular team with the release has now taken an important step in this direction: The official Angular Schmeatics for Bazel has been implemented, with which Bazel can be added to a project via the ng-new command in the CLI.
The Breaking Change that came with the second beta of Angular 7.2 also affects Bazel: In the future, transitive dependencies of
will no longer be automatically installed via
. Instead, they must be manually installed from the workspace file:
In addition to the innovations for Bazel, the release also brings five new features for the router. For the navigation now the type
can be used, also the
now be forwarded to routerLink Directives and
mode is now available. The last new feature again refers to the navigation and concerns the call of objects when navigating back. For more information about the release, see the Changelog on GitHub as usual.
Update from November 29, 2018
The first beta version of Angular 7.2 has two bug fixes . For network errors, the request URL is now output. There was also an innovation related to Ivy: The dependence of the resolution of forward references from the runtime was resolved.
And what about the Ivy Renderer itself? Not much has changed since the release of Angular 7.1. The ten remaining open features that still had to be edited for Angular 7.1 are still incomplete.