Angular 8 : Final Version

Angular 8 Final version was released. The new version comes with many features. Ivy can now be tested, Bazel too.

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 8 Final released

Angular 8 final version is here. As announced, the new version was released in May. Included are previews of Ivy and Bazel, which can be activated manually. Done are the features but not yet, but still in the test phase. Another new feature is the default Differential Loading feature, which creates separate bundles for modern and legacy browsers. There are also innovations in the integration of the Web Worker in the build process of Angular. Upgrades were working on the routing. Manfred Steyer, Trusted Collaborator in the official Angular team, gives an overview of the new features: Angular 8 is here: Ivy-Preview, Service Worker and Differential Loading — these are the new features.

The release candidates of Angular 8

Angular 8.0.0-rc.5

Another release candidate for Angular 8 is available: With Angular 8.0.0-rc.5 something will be done on the upcoming major release. Two new features, two deprecations, a breaking change and a number of bug fixes are included in the release. One of the new features is relevant for anyone still using AngularJS parts in their project. The onUrlChange hook now also detects URL updates triggered by AngularJS. This update is in the context of the Location Services updates released in RC.0, designed to facilitate the upgrade from AngularJS to Angular 8.

The second of the new features for Angular 8 is a stricter typing for SlicePipe. So far, errors ngFor not been found in ngFor since type was issued as any . Now the selection of approved types has been restricted accordingly, so the TypeChecking with Ivy works as intended.

The new release Candidate marked the deprecated integration with the Web Tracing Framework (WTF) and platform-webworker . The Breaking Change @ViewChild and @ContentChild queries, which will no longer be automatically sorted by the compiler in the future, but must be manually marked as static or dynamic. Not affected are @ViewChildren and @ContentChildren .

Bazel has three bugfixes in the release. In addition, problems were fixed in the core and in the router.

Angular 8.0.0-rc.4

When is Angular 8 coming? Perhaps the new major version will be released this month — at least in February, the Angular team had promised. This is supported by the fact that the RC phase at Angular usually stays quite short and that Release Candidate 5 (Angular 8.0.0-rc.4) is already available. The release brings a new feature for Bazel: A container used by the CI has been replaced because a version that was not maintained by the RBE team was implemented so far. This also rbe_autoconfig() support for the rbe_autoconfig() rule, which automatically checks if there are configs for the used toolchain in the @bazel_toolchains repository, or creates them if it does not.

In addition, Angular 8.0.0-rc.4 includes a number of bugfixes. Again, here are some Bazel that will be implemented with Angular 8 as an optional feature. However, most of the bugfixes do not apply to the code, which was mainly used for the static query migration.

Angular 8.0.0-rc.3

The latest release candidate from Angular 8 comes with five bug fixes, which has now been released. The distances will be longer again. Between Release Candidate 1 and 2 were only a few days, now it was more than a week. Two of the fixed issues in Angular 8.0.0-rc.3 are in the router, one in Bazel. Also a bug in the compiler CLI and in the core has been fixed:

• bazel: Bump ibazel to 0.10.1 for windows fixes (# 30196) (9f68c35)
• compiler-cli: log ngcc skipping messages as debug instead of info (# 30232) (548b003)
• core: fix interpolate identifier in AOT (# 30243) (3fe3a84)
• router: ensure history.state is set in eager update mode (# 30154) (9720227)
• router: fix a problem with router not responding to back button (# 30160) (132f01c)

Angular 8.0.0-rc.1 and rc.2

Four bugfixes in two updates that have been released within a few days: The pace on the way to Angular 8 increases. Already one day after the publication of the first release candidate for Angular 8, the second one already appeared. It contains two bugfixes for Bazel. One of these concerns the file metadata.tsconfig.json , which now no longer includes common/upgrade* . The bug that was resolved here occurred because common/upgrade* a dependency that is not included in package.json . The second bug fix is ​​an update of the peerDep Ranges.

The third release candidate of Angular 8, v 8.0.0-rc.2, followed three days later. This version also comes with two bugfixes. In the area of ​​the Language Service, tsserverlibrary was tsserverlibrary from the tsserverlibrary because the symbol should only be used in the context of Types. In addition, there is a bugfix that should avoid problems with Ivy during the update: The Injectable Pipe Migration has been disabled . So far it is not clear whether this mechanism fits Ivy; a detailed plan for the upgrade will follow.

Further information on the release candidates can be found in topic of HelpDev’s Angular tag