grunt-ngmin

on 1.1.5). No need to bring jQuery in for that. If there is indeed a valid reason to bring jQuery into the project, I'd say the responsibility lies more so on the developer ensuring the dependency is met. Minification With the addition of ngmin[5], this isn't necessarily a pitfall just something to consider in your workflow. There is a ngmin grunt task[6] that works as advertised! I've been using it for quite some time now and never an issue. My thought overall though is if you've conceded minification is a step in your project workflow, you'll be using tooling to make that easier. Bring ngmin into the mix and all is well. Directives are never 'done' I would suggest looking into using $watch[7] within the scope of that directive or making use of compile post linking over the linking used in the example. Check out the compile section [8] of the directive guide for more information there. [1] http://docs.angularjs.org/api/ng.directive:ngInclude [2] http://docs.angularjs.org/api/ng.directive:ngShow [3] http://docs.angularjs.org/api/ng.directive:ngHide [4] http://code.angularjs.org/1.1.5/docs/api/ng.directive:ngIf [5] https://github.com/btford/ngmin [6] https://github.com/btford/grunt-ngmin [7] http://docs.angularjs.org/api/ng.$rootScope.Scope#$watch [8] http://docs.angularjs.org/guide/directive