<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Angular on Chris Doing Web</title><link>https://chrisdoingweb.com/tags/angular/</link><description>Recent content in Angular on Chris Doing Web</description><generator>Hugo</generator><language>en-us</language><managingEditor>chris@chrisdoingweb.com (Chris Antes)</managingEditor><webMaster>chris@chrisdoingweb.com (Chris Antes)</webMaster><lastBuildDate>Sun, 05 Jul 2015 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisdoingweb.com/tags/angular/index.xml" rel="self" type="application/rss+xml"/><item><title>Minifying Browserified Angular Modules</title><link>https://chrisdoingweb.com/blog/2015/minifying-browserified-angular-modules/</link><pubDate>Sun, 05 Jul 2015 00:00:00 +0000</pubDate><author>chris@chrisdoingweb.com (Chris Antes)</author><guid>https://chrisdoingweb.com/blog/2015/minifying-browserified-angular-modules/</guid><description>&lt;p class="lead">
 If you&amp;rsquo;ve used &lt;a href="https://angularjs.org/">Angular&lt;/a> in production, you&amp;rsquo;ve probably learned the importance of &lt;a href="https://docs.angularjs.org/guide/di#dependency-annotation">annotating your dependencies&lt;/a> when using a minifier like &lt;a href="https://github.com/mishoo/UglifyJS2">Uglify&lt;/a>: when parameter names get &lt;a href="http://lisperator.net/uglifyjs/mangle">mangled&lt;/a>, Angular&amp;rsquo;s implicit annotation feature breaks. The &lt;a href="https://www.npmjs.com/package/ng-annotate">ng-annotate&lt;/a> package does a great job at alleviating us of this responsibility, but it may need a little hint when you&amp;rsquo;re using something like &lt;a href="http://browserify.org/">Browserify&lt;/a> to organize your code as CommonJS modules.
&lt;/p></description></item></channel></rss>