4 ms·
I have been leading a good sized Angular app for work for the past 8 months, and upgrading from v2 to v4 has been painless, even while having an AOT compilation
by Bahamut 10y ago
I have been leading a good sized Angular app for work for the past 8 months, and upgrading from v2 to v4 has been painless, even while having an AOT compilation build pipeline set up - the only modifications we had to do was switch OpaqueToken to InjectorToken, <template> to <ng-template>, and Renderer usage to Renderer2, and these weren't required to be done yet. We only did those changes to get ahead of the curve from the deprecation messages.
On first note, the codegen size decreased dramatically for AOT compiled builds - we went from ~600 KB vendor + app minified and gzipped (not counting 50 KB of polyfills) to ~400 KB. This is huge, and the boot speed feels even faster on first user load of the page!
Thanks to the Angular team for this fantastic work!
- EugeneOZ 10y agoabsolutely same experience in our case. Painless update with few template to ng-template ctrl+f changes. Angular CLI stabilization is a much more important news, actually. One of mistakes of Angular team - Angular CLI had to be ready before Angular itself.
- bflesch 10y agoNot an angular programmer, but I felt the API docs page didn't load quickly enough.
- doczoidberg 10y agoI also had a painless upgrade from 2.4 to 4.0. With angular-cli ng2 is now usable and in my opinion the best Javacript/typescript framework.
- Bahamut 10y agoI forgot to mention one other change we had to do - we had to switch to the new @angular/animations package, but that was also a pretty simple switch.