Removing Roadblocks in the Move to Angular 4

Angular has become the de facto front-end MVC framework of the web. We had been slowly adopting Angular 1 here at Lucidchart, but the vast majority of our crucial components were built in jQuery and vanilla JavaScript. We were one of the early pioneers of Angular 2. We found Angular 2 compelling because of the improved performance over Angular 1, and the structure, consistency, and productivity that we gained were refreshing after stepping out of the jungle of jQuery. However, we have experienced a few pain points with Angular 2. We use the closure compiler for advanced minification and optimizations, and Angular 2 did not produce a closure compiler compatible with JavaScript. As a result, we had to fork Angular and add closure compatibility. Our bundles that use Angular 2 are also larger than the equivalent jQuery bundles—although they still generally load faster. We were excited for the Angular 4 release because it addresses both of those major pain points.
Our co-founder Ben Dilts and senior engineer Ryan Stringham showcasing our Angular application at Ng Conf 2016.