3 ms·
Is anyone using Angular 2+ in prod? How is it working out and how complicated is it to upgrade 2 -> 3 -> 4...?
by oblio 9y ago
Is anyone using Angular 2+ in prod? How is it working out and how complicated is it to upgrade 2 -> 3 -> 4...?
- dehef 9y agoI use it in prod since 1 year yes. Angular is totally ready to be use in prod since a long time now. Very easy to update: 2-> 4 no gap but my project was starting 4-> 5, very few things on a already big project. In my case the HttpModule, and some internationalization adjustment.
- nicoburns 9y agoIts basically pretty comparable to React at this point. You get a few more things out of the box, and its a fair bit harder to debug (but nowhere near as bad as Angular 1.x). Upgrading is painless (and the upgrades themselves are gradually chipping away at pain points in the lib itself)
- zdragnar 9y agohttps://github.com/angular/angular-cli/issues/8284#issuecomment-341417325 https://github.com/angular/angular-cli/issues/8284#issuecomm... That comment is more or less a recurring experience for me. I've been solving problems that are slightly out-of-the-box of the typical CRUD app, and Angular 2+ has been nothing but pain for me.
- dehef 9y agoYou can transpile with fusebox or ionic cli if angular cli is the problem. For my next project I will use fuseboz with lazy loading (currently I use ionic)
- stupidcar 9y agoWe've just upgraded from 4 to 5 and not had any major problems. Most of the issues we encountered were with the stricter type-checking in TypeScript 2.5, not changes to Angular itself. It took me about a morning to do the upgrade. Overall, using the framework has worked out great. The other front-end frameworks we've used (including ng1) now seem rather toy-like in comparison. The biggest stroke of genius has to the hierarchical dependency injection. Letting a UI component provide injectable services to its children and their descendents instantly solves so much of the tension between integration and reusability that plagued us in the past. And the template language is also brilliant. It actually understands the difference between binding to the string-based attributes of an HTML element, and the object-based properties of a DOM object.
- eitland 9y agoAs long as you stick with the defaults and fix warnings and linter errors it should be mostly painless (<4 hours). This repo is really useful: https://github.com/cexbrayat/angular-cli-diff https://github.com/cexbrayat/angular-cli-diff It lets you diff a simple project generated with different versions of angular-cli; that way you can easily see the any configuration options etc that have changed between releases.