Angular 8 beta 9

Angular 8.0.0 beta 9 is here. The new release not only included a number of bugfixes, but also an upgrade to TypeScript and a change to the HTML parser known as Breaking Change.

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 Beta 9

Update March 20, 2019

With Angular 8.0.0-beta.9, the framework has been upgraded to TypeScript. Angular 8 will require TypeScript 3.3, the previous versions of the JavaScript variant are no longer supported. This innovation represents a breaking change.

Another breaking change from this update concerns the HTML parser. So far, < tr > and < col > automatically supplemented with the corresponding parent element, if that was missing. This auto-correction has been removed with the now released beta. The Angular team has two reasons for this: The behavior of the parser was so far on the one hand opaque and arbitrary, since the same correction rules would have to apply to other HTML elements. On the other hand, the wrapping of the HTML elements was not necessary in some exceptional cases, so that errors could arise due to the behavior of the parser. That’s why there should not be any auto-completion for parent elements of < tr > and < col > in Angular in the future.

In addition to the TypeScript upgrade and behavioral change to the HTML parser, Beta 9 for Angular 8 includes a number of bug fixes. Here again Bazel is in the center of the beta, which includes a total of nine bug fixes. Below are six for Bazel. For example, @angular/upgrade removed from Bazel’s Dev dependencies because it is not needed there, and Angular Schematics for Bazel has received an update and now supports the new project layout for e2e projects.

Further information on Angular 8.0.0-beta.9 can be found in the changelog on GitHub.

Also for those who didn’t read the previous posts you can click our Angular tag and read about

LEAVE A REPLY

Please enter your comment!
Please enter your name here