Then try to not make the modules too small? Sure, if you were ready to make an entire separate application for it it will not be worse when you turn it into on

Then try to not make the modules too small? Sure, if you were ready to make an entire separate application for it it will not be worse when you turn it into one package of a monolith? Also you can build nested structures with modules (like a larger module consisting of smaller submodules). Divide and conquer. This is how abstraction works in a nutshell. You start with a large problem, divide it into smaller parts (modules), each part you treat as a separate problem dividing it into smaller modules, and so on. There exists no need to have a flat application consisting of hundreds of sibling modules. An application might consist of larger modules, then some of those might have smaller submodules (packages), then those might have even smaller ones (classes), then you have methods, then you have statements, then you have function calls, etc. A large monolith does not have to succumb to spaghetti or ravioli-type structuring. A good developer should know how to structure an application of any size.