And so it begins

On the road to Angular 6: Beta season opened!

JAX Editorial Team
Angular 6
© Angular.io / Shutterstock Spring Bine

Angular 6 should be released in 2-3 months. As we’re getting closer to the great finale, we start to see bits and pieces of what is shaping up to be a great version. The beta season for Angular 6 is now opened.

The beta season for Angular 6 is here. Beta.0 has nine bugfixes, three features and one performance improvement.

Features

  • bazel: allow ng_module rules to control whether type checking is enabled (#21460) (cffa0fe)
  • core: add binding name to content changed error (#20352) (d3bf54b)
  • forms: handle string with and without line boundary on pattern validator (#19256) (54bf179)

Performance improvements

  • ivy: add missing dom element in render3_function tree benchmark (#21476) (9b5a485)

 

Update January 10, 2018

We’re one step closer to Angular 6 now that 5.2.0 is here.

There’s not much to say except that it brings four bugfixes. If you’re here for the highlights, here’s what Stephen Fluin wrote in the blog post announcing Angular 5.2.0:

  • Improved type checking for templates
    They’ve added fullTemplateTypeCheck as an angularCompilerOption that uses TypeScript to validate binding expressions in your templates and recommend you enable this flag, as it will become the default in a future major release. Learn more about the various compiler options supported in Angular.
  • Support for TypeScript 2.6
    Angular now supports TypeScript 2.4, 2.5 and 2.6. Check out some of the new features in TypeScript 2.6.
  • Improved Router Param & Data Inheritance
    Previously, nested routes would only inherit parameters and data from parent routes if the parent route did not have a component set. Now paramsInheritanceStrategy can be set to always, meaning child routes will have access to all ancestor parameters and data.

 

Update January 4, 2018

A new year, a new stable version! Let’s ring in 2018 with some bug fixes for the stable release 5.1.3 and the first release candidate of 5.2.0.

5.1.3 Bug Fixes

  • animations: avoid infinite loop with multiple blocked sub triggers (#21119) (3e34fa8)
  • animations: renaming issue with DOMAnimation. (#21125) (d1f4500)
  • common: handle JS floating point errors in percent pipe (#20329) (fa0e8ef), closes #20136
  • language-service: ignore null metadatas (#20557) (48a1f32), closes #20260
  • router: fix wildcard route with lazy loaded module (again) (#18139) (8c99175), closes #13848

5.2.0 Bug Fixes

  • animations: avoid infinite loop with multiple blocked sub triggers (#21119) (86a36ea)
  • animations: renaming issue with DOMAnimation. (#21125) (871ece6)
  • common: handle JS floating point errors in percent pipe (#20329) (07b81ae), closes #20136
  • language-service: ignore null metadatas (#20557) (3e47ea2), closes #20260
  • router: fix wildcard route with lazy loaded module (again) (#18139) (5ba1cf1), closes #13848

Update December 21, 2017

Angular 5.2.0 beta.1 is here.

Bug Fixes

  • compiler: generate the correct imports for summary type-check (d91ff17)
  • forms: avoid producing an error with hostBindingTypeCheck (d213a20)

Features

  • compiler: allow ngIf to use the ngIf expression directly as a guard (82bcd83)
  • router: add “paramsInheritanceStrategy” router configuration option (5efea2f), closes #20572

 

Update December 14, 2017

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 StaticInjectorError message (#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.

What’s new?

  • 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

If you want to see the full list of features and bugfixes, see the AngularMaterial, and CLI changelogs.

Angular Material

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.

Stephen Fluin

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.

Angular Universal

To add Universal in your current CLI application, you can now use the following commands in your project:

 

 

Replacing <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:

 

 

App Shell

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 /shell.

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.

Feature:

  • compiler: introduce TestBed.overrideTemplateUsingTestingModule (a460066), closes #19815

The second beta brought 10 bugfixes and the third beta brought the same number of bugfixes plus a feature.

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 registerLocaleData (#20623) (24bf3e2)
  • 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.

Comments
comments powered by Disqus