@MagedAhmad

I am starting a new major open source project based on Laravel, and I want to use modules. I have tried all three of the other modules packages I have found and not been completely happy with any of them by in the end I have settled on a combination of Internachi Modular and Wikimedia's Composer Merge plugin to provide this functionality.

So I read about this package with some interest. I have not yet tried it out - and may never do so - but I do have some comments / questions:

Snowflakes

I have already started using UUIDs for my tables - and I have looked at ULIDs and rejected them as a bit new - but snowflakes would (as you suggest) be even better. May I recommend that you create an separate package that will only provide Laravel support for snowflakes (i.e. in migrations and in models/factories etc.) using Traits and macros?

(I am also unclear where snowflakes come into modularisation.)

General description

What sets this package apart from others that provide similar functionality?

I am looking for a package which does the following:

• Straight forward modules (obviously)
• Nested sub-modules
• Composer / Laravel autoload only of modules required for the specific web call / artisan CLI call. In simple terms, for performance reasons in very large projects, I am looking for the coder to be able to define which php files need to be autoloaded (import) at initialisation, and then have middleware to autoload additional files depending on the Route chosen.
• Comprehensive support for all types of php and JS files to be modularised including all parts of Laravel and all major front-end technologies (blades, livewire, vue, etc.).

If the scope of what you are trying to achieve matches the above, I would be happy to assist with coding, testing, fixing etc.