Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Introduction of Angular 4

DZone's Guide to

Introduction of Angular 4

Angular 4 has been out for a little over a month, but if you haven't had the chance to look into it, here's some of the best the new features Angular.

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

From the title of the article itself, as a tech geek, you may be worried about similar experience between transformation from Angular 1 to Angular 2.

But don't worry, this time it's more of a version number change, with some new features rather than a complete framework level change like what we saw with the transition form Angular 1 to Angular 2. This release is backward compatible with 2.x.x for most applications.

Some notable features of this version include:

  1. Template binding syntax improvements.

  2. Improved *ngIf and *ngFor, users can now use an if..else style syntax.

  3. Animation package pulled out from @angular/core and added as a new package @angular/platform-browser/animations.

  4. TypeScript 2.1 and 2.2 compatibility.

  5. Source Maps for templates, that give meaningful context in terms of the original templates.

As per Igor Minar in Keynotes, the team plans to do major releases in 6 months interval while keeping large-scale changes to a minimum. It seems like a pretty feasible plan unless another mistake occurs with the naming of the packages like what happened with the router package.

The Angular team announced that they will be using Semantic Versioning Specification (SemVer) - when releasing updates, and their updates will follow the below patterns:

1. Patches: Released every week with the exception of holidays.
2. Minor updates: Released every month.
3. Major updates: Released every six months; i.e two major releases every year.

Conclusion:
There are main important messages attached with the Angular 4 here:

1. Nothing to worried about in terms of framework level changes like what was experienced in transitioning from Angular 1 to Angular 2.
2. The goal of the backward compatibility promise is to ensure that changes in the core framework and tooling don't break the existing ecosystem.

Enjoy!

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.

Topics:
angular 4 ,javascript ,typescript ,web dev

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}