On the road to Angular 6: 5.2.0 — Tis the beta season to be jolly
Angular 5’s aim is to continue the team’s focus on making it smaller, faster, and easier to use. But even though we’re still in awe of the release, it’s business as usual for the Angular team. Case in point: the beta season for 5.2.0 has officially begun.
Why settle for Angular 5.1.0 when you can have 5.2.0?
The beta season for Angular 5.2.0 has officially begun — the first beta brings five features, namely
- animations: re-introduce support for transition matching functions (#20723) (590d93b), closes #18959
- compiler: add a pseudo $any() function to disable type checking (#20876) (70cd124)
- compiler: narrow types of expressions used in *ngIf (#20702) (e7d9cb3)
- core: add source to
StaticInjectorErrormessage (#20817) (b7738e1), closes #19302
- forms: allow nulls on setAsyncValidators (#20327) (d41d2c4), closes #20296
Update December 7, 2017
Angular 5.1.0 is here. Although it only brings three bugfixes, the Angular 6 machinery is now in motion.
Angular 5.1 is not the only good news though — Stephen Fluin, developer advocate at Google announced in a blog post that the team also released v1.6 of the Angular CLI, and the first stable release of Angular Material.
- Angular Material & CDK Stable Release
- Service Worker support in the CLI
- Improved Universal & AppShell Support in the CLI
- Improved decorator error messages
- TypeScript 2.5 support
What does it take to reach version five of Angular Material? 11 alpha releases, 12 beta releases, and three release candidates. Furthermore, the CDK has finally graduated from Angular Labs.
Starting with this release, Angular Material will be following the same SemVer philosophy as Angular, with major versions of Angular Material and Angular CDK releasing at the same time as major versions of the rest of the platform. Patch releases will follow a weekly cadence, while minor feature releases will become available as features are completed.
CLI 1.6 Service Worker Support
Angular 5.0.0 shipped with a new Service Worker implementation customized for Angular applications. According to Fluin, Angular CLI 1.6 includes support for building applications which take advantage of this new feature. Using
@angular/service-worker can improve the loading performance of your applications in browsers which support the API, and make your application’s loading experience more like that of a natively installed app, he added.
CLI 1.6 Improved Universal & App Shell Support
The release of Angular CLI 1.6 brings better support for adding Universal to your existing projects via Schematics and App Shell support.
To add Universal in your current CLI application, you can now use the following commands in your project:
<name> with the name you want to give your universal app. This will take your current application and create a Universal module, and configure your
angular-cli.json file automatically for you. You can then skip to step 4 in the guide to using universal.
To build your Universal app, simply run the following command:
You can generate and build an application shell, which uses a special universal build to create a static first render of your application in your
index.html. The outcome is that you’ll have a better experience while your application is being bootstrapped.
Make sure you have a
RouterModule imported in your application’s
NgModule, and a
<router-outlet></router-outlet> in your application component’s template. App Shell uses the router to render your application.
The next step is to run this command:
This will add support for the app shell to your
angular-cli.json main application, using the universal application passed in argument. If the universal app isn’t passed in, it will create a universal application by running the universal schematic first. The route argument specify the route to generate during build (router is required for App Shell support). By default this is
After this, just build your application as normal using
ng build and the
index.html file will include the route from your application automatically rendered for you.
There’s also support for TypeScript 2.5, improved decorator error messages and more. Check out Stephen’s blog post for the complete list of highlights.
Update December 6, 2017
Angular 6 should be released in March or April 2018. As Karsten Sitterberg pointed out in his post detailing version 5’s most exciting features, “the Angular team already has announced that the latest version’s focus applications should be even faster at runtime and more compact in delivery. Until then, it’s likely that experiments from the Angular-Labs will be stable and adopted into the framework or AngularCLI.”
SEE ALSO: What’s new in Angular 5?
Now that Angular 5 is here, it’s time to look toward the future, which happens to be all about Angular 6. What will this version bring? We don’t know yet but we’re pretty excited to see the bits and pieces and then put everything together next spring.
That said, it’s time to move on — to 5.1.0 to be more exact. The first beta arrived in early November with six bugfixes and a feature in tow.
The second beta brought 10 bugfixes and the third beta brought the same number of bugfixes plus a feature.
The first release candidate was released on the 1st of December; it brought over a dozen bugfixes and a couple of features:
- common: add locale id parameter to
- compiler-cli: improve error messages produced during structural errors (#20459) (8ecda94)
The second release candidate was also released on the 1st of December and brought five more bugfixes.