v360tech / laravel-module-installer
Installs: 14
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 0
Forks: 34
Type:composer-plugin
pkg:composer/v360tech/laravel-module-installer
Requires
- php: 7.* || 8.*
- composer-plugin-api: ^2.0
Requires (Dev)
- composer/composer: ^2.0
- mockery/mockery: ~1.0
- phpunit/phpunit: ~8.0 || ~9.0
This package is auto-updated.
Last update: 2025-10-04 07:48:34 UTC
README
Originally forked from https://github.com/joshbrw/laravel-module-installer
The purpose of this package is to allow for easy installation of standalone Modules into the Laravel Modules package. This package will ensure that your module is installed into the Modules/ directory instead of vendor/.
You can specify an alternate directory by including a module-dir in the extra data in your composer.json file:
"extra": { "module-dir": "Custom" }
By default the name of the module will be extracted from the package using the convention <namespace>/<name>-module, for example v360tech/user-module would install into Modules/User. However the name of the module can be customized via extra data in your composer.json file:
"extra": { "module-name": "MyUser" }
Now above module will be installed into Modules/MyUser.
Installation
- Ensure you have the typeset tolaravel-modulein your module'scomposer.json
- Require this package: composer require v360tech/laravel-module-installer
- Require your bespoke module using Composer. You may want to set the constraint to dev-masterto ensure you always get the latest version.
Notes
- When working on a module that is version controlled within an app that is also version controlled, you have to commit and push from inside the Module directory and then composer updatewithin the app itself to ensure that the latest version of your module (dependant upon constraint) is specified in your composer.lock file.