More on upcoming releasesįirst good thing is, the Angular people said they are not going to release any version with that drastic changes which is there between version 1.X and 2. To avoid this confusion they decided to skip the version 3 and release with version 4.0.0, so that every major dependency in the MonoRepo are on the right track. Now releasing Angular as version 3, with it’s route on version 4 will create confusion (this confusion is already there, that’s why they want to resolve it). And that’s because of some active and huge developments on the router section, like route-preload. Now the problem is with the which is already in a 3.X version.
All angular versions code#
The advantage of MonoRepo is, you don’t have to deal with the versioning of the code dependencies. etc are in the same repo and may have there own versions. But we never guarantee bugs :P Why that new version is not 3?Īngular is being developed in a MonoRepo. Upgrading the typescript version lead Angular to release a new major version.
All angular versions upgrade#
So, technically if Angular upgrade itself from TS 1.8 to TS 2.1, it is a breaking release even though there won’t be any extra breaking changes by the Angular developers. Now TS 2.1 has breaking changes with respect to TS 1.8. Why I said probably not, is because of the reason why Angular is moving into the next major version.Ĭurrently Angular uses Typescript 1.8 and planning to upgrade to 2.1 (or probably 2.2) of Typescript. So any breaking changes in the next Angular? For new features, without any breaking changes the second number in the version will get changed and all the breaking change releases will be with the change of the first number of the version.
All angular versions Patch#
Probably you already know about semantic versioning, the image below also describes it.Īs shown in the image, the last number will indicate the patch releases, which means small bug fixes etc. This scary feeling about Angular releases still exists today and that’s the reason when Google said it’s going to release the next major versions soon, people started thinking they will again have something big and drastic changes.įortunately, this time it’s not the case Why another major release?įirst of all, let me explain how the version will work for Angular from now on. Even today I can see the industry is still in 1.6 because they are not really in a position to upgrade their applications.
That means a hell lot of work for those who want to upgrade from 1.X to version 2. Even the concept of data flow, binding, routing etc. Since the time Angular 2 was in alpha, there was a terror among some people out there in the community (including me) as the new angular was being written and will be best usable with typescript. AngularJS means version 1.X and Angular means the version 2 and beyond. Atleast that’s how the official people address it now.
Angular people worked really hard on the version 2 of AngularJS… Sorry, not AngularJS, but Angular.
0 kommentar(er)
