<?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 Zach Alexander</title><link>https://zpalexander.com/tags/angular/</link><description>Recent content in Angular on Zach Alexander</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 Jan 2016 20:09:00 -0800</lastBuildDate><atom:link href="https://zpalexander.com/tags/angular/index.xml" rel="self" type="application/rss+xml"/><item><title>Debugging "Unknown Provider" In Minified Angular.js</title><link>https://zpalexander.com/posts/debug-unknown-provider-minified-angularjs/</link><pubDate>Wed, 27 Jan 2016 20:09:00 -0800</pubDate><guid>https://zpalexander.com/posts/debug-unknown-provider-minified-angularjs/</guid><description>&lt;p&gt;For the past few months I’ve been working on an &lt;a href="https://angularjs.org/"&gt;AngularJS&lt;/a&gt; app that makes use of &lt;a href="https://material.angularjs.org/latest/"&gt;Angular Material&lt;/a&gt; as a Bootstrap-like front-end library. I recently had to solve one of the hardest bugs I’ve ever faced in Angular, and I’d like to share my debugging technique with anyone who might encounter the same problem down the road. While the bug was related to the use of Angular Material in my case, it could occur in vanilla Angular as well, so don’t stop reading just yet!&lt;/p&gt;</description></item></channel></rss>