Compare Laravel Package Generators

I would like to briefly discuss the improvements we have made compared to other Laravel package generators.

Filefabrik/paxsy is mainly inspired by InterNACHI/modular. For us, InterNACHI/modular was the Laravel package generator that produced the best results without much fiddling.

After some time with InterNACHI/modular, we had further requirements for a Laravel Package Generator, not at least the compatibility with Laravel 11.

The reference version we refer to for InterNACHI/modular is this version: https://github.com/InterNACHI/modular/releases/tag/2.2.0

Laravel Prompts

Usage with Laravel Prompts but also keep the native cli-commands

Separating generator and bootloader

We have split the Laravel package generation into two software parts.

Paxsy as Laravel Package and Component Generator

The underlying generator is paxsy. Paxsy’s job is exclusively responsible for creating the packages and components. Paxsy should only be used as a dev-dependency. (It makes no sense to use a generator tool in a Laravel production environment)

Bootraiser as Bootloader

Bootraiser as a separate package whose only task is to load Laravel packages and package components into Laravel.

This increases the maintainability of the Paxsy generator on the one hand, and on the other hand, generators and bootloaders are two completely different software aspects You use your Laravel packages without the dependency on paxsy.

Different Namespaces

We usually develop Laravel packages in a Laravel developer installation. For various customers with various packages at different times.

Example:

CustomerElectricity/parts as composer package customer-electricity/parts TicketStoreCustomer/concerts as composer package ticket-store-customer/concerts

Switchable Output-Folders

….coming soon