Modularizing your application is a good practice because it makes the components reusable, configurable and testable.<\/p>\n
As we know that angular is on the global scope itself whereas angular.module is a global place to create, register or retrieve angular modules. In other words, \u00a0angular.module is a container for other units of your angular application like services, controllers, providers, constants etc.<\/p>\n
[js]
\n angular.module(name, [requires], [configFn]);
\n[\/js]<\/p>\n
angular.module must have a name. It can also contains dependencies enclosed in brackets ([]) as second parameter and an optional configurable function.<\/p>\n
\u00a0NOTE:<\/strong> If dependencies brackets ([]) are specified then new module is being created. Otherwise the module is being retrieved for further configuration.<\/p>\n [js] It creates a new module having name myAppModule_1 and service ‘service_1’.<\/p>\n <\/p>\n [js] It overwrites module ‘myAppModule_1’ by creating a new module having name myAppModule_1 and service ‘service_2’.<\/p>\n <\/p>\n [js] It will update module ‘myAppModule_1’ adding a new service ‘service_3’.<\/p>\n Best Practice to create an angular.module<\/strong><\/p>\n [js] …
\nangular.module(‘myAppModule_1’, []).service(‘service_1’,function(){});
\n[\/js]<\/p>\n
\nangular.module(‘myAppModule_1’, []).service(‘service_2’,function(){});
\n[\/js]<\/p>\n
\nangular.module(‘myAppModule_1’).service(‘service_3’,function(){});
\n[\/js]<\/p>\n
\n\/\/NOTE: the immediately invoked function expression is used to exemplify different files and is not required
\n(function(){
\n\/\/using the function form of use-strict
\n"use strict";
\n\/\/Pass a second parameter ONLY THIS ONE TIME because
\n\/\/Re-declaration of second parameter creates bugs which are difficult to detect
\n angular.module(‘myApp’, [‘ngResource’, ‘ngAnimate\u2019]);<\/p>\n
\n})();
\n[\/js]<\/p>\n