Angular 8 updates: Two Release Candidates with four bugfixes

Something is happening at Angular 8 updates: Two new Release Candidates are here! However, the two versions bring only a few changes. What has happened with Bazel and Ivy, the two great upcoming features?

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 updates: rc 1 and 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 the changelog on GitHub as well as all the previous posts for the Angular 8 release series can be found here.

LEAVE A REPLY

Please enter your comment!
Please enter your name here