http://plnkr.co http://plnkr.co is an Angular app used by many Angular users. I would say it has a more sizable codebase than most open-source Angular projects.

http://plnkr.co http://plnkr.co is an Angular app used by many Angular users. I would say it has a more sizable codebase than most open-source Angular projects. The organization that has worked for me (at this scale) can be seen at: https://github.com/filearts/plunker_www/tree/master/assets/js https://github.com/filearts/plunker_www/tree/master/assets/j... Organizing by feature, while great on the surface, is a challenge when the majority of code is designed for re-use anywhere in the app. As a result, each file is its own module in Plunker. In the WIP rewrite you have modules like "plunker.directive.aceEditor" that will contain a mix of directives and services necessary to interact with the ace editor in the Angular world. In this sense, you could say that code is organized by 'feature' if feature is very narrowly defined. Understanding a body of code under this approach is relatively simple since the modules required by a given module must be listed for Angular's DI to work. The required modules' names correspond directly to the physical location of the code so navigating is pretty simple. That being said, there is still lots of room to improve and Plunker is by no means a 'large project' (it is made by a team of 1 person).