Weave Code
Modularity Laravel Package
unusualify/modularity
Unusualify Modularity is a Laravel package for building modular applications with reusable, self-contained modules. It provides module discovery, service provider registration, config and route loading, and a structured foundation for organizing large Laravel projects into maintainable packages.
unusualify/modularity brings a clean, scalable module architecture to Laravel applications. It helps organize large projects into self-contained modules, each with its own routes, views, migrations, config, and service providers, while keeping integration with the core framework straightforward.
- Generate and register modules with Artisan commands
- Isolate routes, migrations, views, and config per module
- Autoload module service providers and resources
- Keep modules reusable and easy to enable or disable
- Simplify maintenance of large Laravel codebases
Frequently asked questions about Modularity
- What is unusualify/modularity used for in Laravel?
- unusualify/modularity is a Laravel package for building large applications from self-contained modules. Each module can carry its own routes, controllers, models, migrations, and views, so teams can keep code organized by domain. It is aimed at modular monolith or HMVC-style Laravel applications where registration, scaffolding, and module management matter.
- How do I install unusualify/modularity with Composer?
- Install it as a Composer dependency in a standard Laravel project, typically with composer require unusualify/modularity. Confirm the version constraint against your Laravel and PHP versions before updating. After installation, clear Laravel caches and run any package migrations if the package documentation instructs you to do so.
- Which Laravel and PHP versions does unusualify/modularity support?
- The provided overview does not list explicit Laravel or PHP version constraints for v12.11.1. Check the package composer.json and README for the authoritative support matrix before adopting it. Semver 12.11.1 implies backward compatibility within the major version, but you should still verify constraints against your application.
- Is unusualify/modularity a good alternative to nwidart/laravel-modules?
- Both packages address Laravel modularization, but they may differ in module conventions, scaffolding commands, and front-end assumptions. unusualify/modularity is positioned around self-contained modules with routes, controllers, models, migrations, and views. Evaluate it against your existing module structure and test one pilot module before treating it as a drop-in alternative.
- How do I create or scaffold a new module in Modularity for Laravel?
- The package is described as supporting module registration, scaffolding, and management. The exact command names and generated file layout are not included in the provided overview, so consult the README or package source. Start with one pilot module and confirm how routes, controllers, models, migrations, and views are registered before scaling out.
- Does unusualify/modularity v12.11.1 have breaking changes?
- The v12.11.1 release is described as patch-level with bug fixes and no advertised breaking changes, new features, or deprecations. However, the fixes target the submit method, and validation or async handling changes can alter behavior even when labeled as fixes. Diff any custom submit overrides against the changed implementation before merging.
- What changed in the Modularity submit method in v12.11.1?
- The assessment says the v12.11.1 fixes target the submit method, making form and action submission a key integration surface. The provided details do not specify whether public signatures, return types, events, exception behavior, or async semantics changed. Inspect the changelog and diff the submit implementation, especially if your application overrides it or customizes validation.
- Can I use unusualify/modularity with Inertia, Livewire, Vue, or Blade?
- The package supports modules with their own views, and it is intended for Laravel applications that want module encapsulation. The provided overview does not confirm specific front-end integrations such as Inertia, Livewire, Vue, or Blade conventions. Confirm that the package's front-end and form conventions match your existing stack before adopting it broadly.
- How should I test a Modularity upgrade for validation and form submissions?
- Create a branch, update the Composer constraint, and run composer update for unusualify/modularity. Clear Laravel caches, run any applicable migrations, and execute your application test suite with focus on form submission and validation paths. Add regression tests for validation failures, successful submissions, duplicate submissions, and async behavior if your forms rely on it.
- What are the production risks of using Modularity for Laravel modules?
- The main risks called out are validation regressions, async race conditions, double submissions, unhandled promise or fetch errors, and silent behavior changes in custom submit handlers. Secondary risks include version drift and undocumented coupling to package internals. Monitor request latency, error rates, and duplicate-submission behavior under load, and keep a rollback pin available.
Weaver
How can I help you explore Laravel packages today?