Should there be more than one module in an angular application?

Question

JavaScript

It's about app.module Is
it done only once ?
And you can use the example of an online store, let's say, to give what modules there may be mandatory in order to take them out separately. Because I always represented, say, a basket with modules and made a factory for it, for example, and this turned out to be a module in my understanding. Or, for example, a page can be a module?

Answer 1

Angularjs is designed for single page applications - spa. You can make each section of the application into a separate module. Moreover, each functional block not related to the logic of the section is in a separate module, and even just sets of more or less universal directives and services are placed in separate modules.
The module is essentially a namespace in this case, the names will be services, directives, controllers, etc.
By connecting a module, you give the opportunity to use its services in your module via DI