PHPackages                             jackwander/laravel-module-maker - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. jackwander/laravel-module-maker

ActiveLibrary[Utility & Helpers](/categories/utility)

jackwander/laravel-module-maker
===============================

A zero-config custom module creator for Laravel 11 projects.

2.3.0(3mo ago)0282↓50%MITPHPPHP ^8.2

Since Aug 29Pushed 3mo ago1 watchersCompare

[ Source](https://github.com/jackwander/Laravel-Module-Maker)[ Packagist](https://packagist.org/packages/jackwander/laravel-module-maker)[ RSS](/packages/jackwander-laravel-module-maker/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (4)Dependencies (3)Versions (22)Used By (0)

Laravel Custom Module Creator
=============================

[](#laravel-custom-module-creator)

This package provides a robust, modular architecture for Laravel applications. Designed for consistency and maintainability, it allows you to build features in isolation within the `app/Modules` directory.

> **🚀 Zero-Config:** As of v2.0.0, this package automatically handles PSR-4 autoloading, Service Provider registration, and API route discovery. No manual `composer.json` or `app.php` edits are required.

---

📋 Requirements
--------------

[](#-requirements)

RequirementSupported Versions**PHP**`^8.2`**Laravel**`^11.0`---

📦 Installation
--------------

[](#-installation)

```
composer require jackwander/laravel-module-maker
```

---

🏗️ Architecture & Inheritance
---------------------------------

[](#️-architecture--inheritance)

To keep your application maintainable and scalable, this package encourages an **Intermediate Base Class** (Bridge) pattern. This allows you to customize global behavior—like custom response formatting or shared business logic—without ever touching the `vendor/` directory.

### The Inheritance Chain

[](#the-inheritance-chain)

Your generated modules follow this hierarchy:

**`Vendor Base`** ➜ **`App Core`** ➜ **`Module File`**

1. **Vendor Base:** The raw logic provided by the package inside `ModuleMaker/Resources` (Read-only).
2. **App Core:** Your custom bridge where you add project-specific logic (Editable).
3. **Module File:** The specific logic for a feature (e.g., `PersonService`).

---

⚙️ Configuration & Customization
------------------------------------

[](#️-configuration--customization)

By default, the generator extends the package's internal resources. To take full control of your architecture, follow these steps to use your own custom "Core" files.

### 1. Publish the Configuration

[](#1-publish-the-configuration)

Publish the config file to your application's config directory:

```
php artisan vendor:publish --provider="Jackwander\ModuleMaker\ModuleServiceProvider" --tag="config"
```

### 2. Create Your Core Layer

[](#2-create-your-core-layer)

We recommend creating a `Core` directory to house your bridge classes at `app/Modules/Core/`. Create a file (e.g., `BaseService.php`) and extend the package's resource:

```