Level 104
What is the issue exactly, the ->group(__DIR__ . '/../routes/web.php')?
Can you show the package's composer.json?
Aug 29, 2025
8
Level 8
Autoload SUCKS
I keep running into problems in auto load. I have created my own package structure which look like this
└───ecommerce
└───src
│ composer.json
│ package.json
│ vite.config.js
│
├───app
│ ├───Http
│ │ ├───Controllers
│ │ │ EcommerceController.php
│ │ │
│ │ └───Models
│ │ Product.php
│ │
│ └───Models
├───databases
│ ├───migrations
│ │ 2025_08_29_123456_create_products_table.php
│ │
│ └───seeders
├───Providers
│ EcommerceServiceProvider.php
│
├───resources
│ └───js
│ │ ecommerce.jsx
│ │
│ ├───components
│ │ ProductCard.jsx
│ │
│ └───Pages
│ └───Products
│ Index.tsx
│
└───routes
web.php
and I have three files, routes, controller, and Service Provider which seems to be the problem.
Service Provider
<?php
namespace Ecommerce\Providers;
use Illuminate\Support\ServiceProvider;
use Illuminate\Support\Facades\Route;
class EcommerceServiceProvider extends ServiceProvider
{
// ...
protected function registerRoutes()
{
Route::middleware('web')
->namespace('Ecommerce\App\Http\Controllers')
->group(__DIR__ . '/../routes/web.php');
}
}
Routes
<?php
use Illuminate\Support\Facades\Route;
use Ecommerce\App\Http\Controllers\EcommerceController;
Route::get('/ecommerce', [EcommerceController::class, 'index']);
Controller
<?php
namespace Ecommerce\App\Http\Controllers;
use App\Http\Controllers\Controller;
use Inertia\Inertia;
class EcommerceController extends Controller
{
public function index()
{
return Inertia::render('Ecommerce/Index');
}
}
I don't know why this is a problem if I hard code the file address it gets around the problem but I don't want to do it this way. It even has AI stumped.
Level 50
Are you calling that registerRoutes() method somewhere? I don't see a boot() method in your provider.
I've always registered package routes the way that's shown in the docs:
1 like
Level 8
I got it working, it flipping sucked *** but its working, so I can carry on from here. Module based packages using Inertiajs
Level 7
Are you creating a package or are you using a modular approach for a Laravel app? Because in both cases, your directory structure is not very conventional.
Usually, when creating a composer package for Laravel, composer.json and so on are in the root, and you have an src folder with the package classes, services and so on, but there is no need to have app. Meaning, you have src/database, src/Routes and so on inside the root folder of the package. Similar structure I have seen in a modular Laravel structure.
In brief, in the above tree, move everything under src to ecommerce and then rename app to src. Also, move database, resources and routes to the root folder (ecommerce). This way, your structure will resemble a Laravel application folder tree (except that app is named src).
Level 4
If this is a package, I think there might be a few issues..
It seems like you're trying the mimic application convention, and apply it to a library. It doesn't work like that. Not auto-magically, there still have to be hooks/hints.
The composer.json file, package.json, etc... if the root of your project is ecommerce and not src, they in wrong place.
Does the composer file hint at how to load the service provider. Does it have the right namespacing for PSR-4, it's easy to leave out a couple of \'s. I've done it lots.
Also, how did you add it to composer, did you have composer symlink local or use something like satis? If you just put it in the vendor folder, composer won't know it's there.
Also, @merklin response highlights perfectly the structure of a library, such as, composer in the root.
Level 8
Yes, I thought I wanted it as a package in the first place, but I tried a package called Laravel Modules, with Modules I was not able to get it to work with InertiaJS, so I created it myself so I knew what was happening under the hood.
I basically want it so I can create a module, and if a module is finsihed, I can easily copy that module over to another file (laravel app) for the customers need.
I will create the thing I made now as a laravel package, and call it laravel hot swap.
PS I am open to suggestions.
Level 80
I have three files, routes, controller, and Service Provider which seems to be the problem.
@randy_johnson You didn’t actually say what the problem was, though?
Level 8
@martinbean that is a very very good point. I need to do better.
Please or to participate in this conversation.