You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 6, 2019. It is now read-only.
Yes, for large-scale app I expect you would want to split filters, controllers etc. into separate files and use requireJS in development to get them into browser and for tests.
Now depending on how large your application really is you need to decide on what strategy you'll use for production. For most projects it would be use almond JS and build a single, minified version of a final delivery file (something I will include in future version of the project). However for really large applications where a combined, minified version would weight more than say 500K I would consider delivering your controllers and templates separately as needed.
Hope this helps a little, good luck with your project!
Does it make sense to split the modules out into filters, services, directives, etc... how would that scale out for a large-scale JS app?
The text was updated successfully, but these errors were encountered: