- What is torann/modules used for in a Laravel application?
- Torann Modules is a lightweight package for splitting a Laravel application into reusable, self-contained modules. Each module can ship its own service providers, routes, views, and configuration so that larger projects stay structured and maintainable. It is intended as a basic module implementation rather than a full-blown CMS or multi-tenancy framework.
- How do I install torann/modules with Composer?
- Install it with composer require torann/modules, then publish the package assets so configuration lands in your application. Because the package is pre-1.0, pin an exact version in composer.json rather than using a caret constraint. Validate the published config against the package defaults before committing it.
- Which Laravel and PHP versions does torann/modules support?
- The available release notes do not document a supported Laravel or PHP version matrix, so treat this as an open question rather than a guarantee. Check the require and conflict blocks in the package composer.json and compare them against your application's framework version. Also confirm whether those constraints are actually enforced, since unenforced constraints can install into incompatible environments.
- Is torann/modules stable enough for production use?
- The package is at 0.1.x, which means the public API should be considered unstable and breaking changes may appear between minor versions. Pin exact versions and treat every version bump as a review gate in your dependency workflow. It can be reasonable for a greenfield Laravel service if you accept that upgrade discipline.
- What changed in torann/modules version 0.1.1?
- Version 0.1.1 added a more flexible stub system, added a tenant option to the migration command, and fixed a bug with publishing configuration. Two of those three items are developer-experience fixes, which suggests the package is still maturing its scaffolding layer. The tenant migration option is the most consequential change because it touches schema management.
- Does torann/modules support multi-tenancy?
- The 0.1.1 release added a tenant option to the migration command, which signals multi-tenancy aspirations rather than a fully documented tenancy model. It is not clear whether that option assumes a specific package such as stancl/tenancy or spatie/laravel-multitenancy, or whether it targets schema-per-tenant versus shared-schema. Confirm alignment with your own tenancy approach before enabling the flag, and leave it off if you have no tenancy requirement.
- How do I customize the stubs and published config from torann/modules?
- Publish the package assets into your application and commit them so they are reviewed like any other change. The flexible stub system lets you align generated code with your house conventions instead of fighting the defaults. Once customized, assign an owner, because upgrades can silently leave your stubs and config behind the new package defaults.
- How should I test torann/modules before rolling it out?
- Adopt it in a non-production branch first and run vendor:publish into a clean environment to verify the config publishing fix rather than trusting the release notes. Diff the published config against the package defaults, then exercise the migration command both with and without the tenant flag against a disposable database. Only promote once you have confirmed behavior matches your schema workflow.
- How does torann/modules compare to other Laravel module packages?
- This evaluation does not include a head-to-head comparison with alternatives, so any decision should be based on your own requirements. The distinguishing points here are the flexible stub system and the tenant option on the migration command. Weigh those against each alternative's release history, version constraints, and maintenance cadence before choosing.
- Is torann/modules actively maintained?
- The available information shows a 0.1.1 release but no published changelog history, upgrade guide, or release cadence, so there is no track record to rely on. Review commit frequency, open issue volume, and bus factor on the repository before adopting. Treat the missing framework-version constraints and changelog as gaps that need verification, not as a clean bill of health.