While this won't help you with your current compilation problem, I suggest that in the future, as a preventative measure, you do a production compile on a frequent basis.
Running the app in non-prod mode causes much of the code to be compiled on the fly in the browser at runtime, and, as you have found, misses many issues that will fail a full production compilation. For example, I had an issue yesterday where a component's template referred to a non-existent member variable. So, you should probably do a production compile after the addition of any major feature, and more often if possible. One way to do that is to use a Continuous Integration (CI) sever, such as Jenkins or Hudson, set up to poll your SCM repo, and build whenever there are changes. Frequent prod builds will alert you to these issues early, when there are fewer changes, and the problem is easier to find. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
