Weave Code
Domain Maker Laravel Package
phpsquad/domain-maker
Domain Maker is a Laravel package for scaffolding domain-driven design structures. Use Artisan commands to generate domains, actions, DTOs, models, and related classes, keeping business logic organized and your application easier to maintain.
Domain Maker makes Domain Driven Development easier in Laravel by providing you with a set of commands to create the scaffolding and boilerplate laravel normally provides but tailored to a Domain Oriented Structure.
Frequently asked questions about Domain Maker
- How do I install phpsquad/domain-maker in a Laravel application?
- Install it with Composer as a development dependency, for example composer require --dev phpsquad/domain-maker. Laravel package discovery registers the service provider automatically, so no manual provider entry is needed. Because the repository is archived, pin an exact version and validate the Composer constraints against your Laravel and PHP versions before committing.
- Which Laravel and PHP versions does Domain Maker support?
- The last release dates to December 2022 and targets the Laravel 9 and 10 era. The repository is archived, so no compatibility patches will arrive for Laravel 11, Laravel 12, or newer PHP versions. Run a compatibility spike on a throwaway branch against your full version matrix before adopting it.
- What Artisan commands does Domain Maker provide?
- It provides Artisan commands that scaffold domains, actions, DTOs, models, and related classes. The generated files follow a domain-oriented layout, typically separating domain, application, and infrastructure concerns. All output is ordinary PHP that your application owns and can edit freely.
- Is Domain Maker safe to use in production?
- Yes, in the sense that it has no runtime surface: it is a dev-time scaffolding package that only registers Artisan commands. Install it under require-dev so it never ships to production. The real risk is lifecycle, not security, since the package is archived and will not receive updates.
- Is phpsquad/domain-maker still maintained?
- No. The GitHub repository is archived, has roughly 87 stars, and shows an effectively single-maintainer history with no CVE process or roadmap. Treat it as a frozen dependency and either fork it internally or cap how much of your codebase depends on it. Budget a few hours per Laravel major if you choose to maintain a fork.
- How is Domain Maker different from Laravel's built-in make commands?
- Laravel's make:* commands generate classes into the default app directory structure, which suits vanilla MVC. Domain Maker tailors the same kind of boilerplate to a domain-oriented folder layout so new code lands in the right bounded context. It codifies a convention rather than enforcing an architecture.
- Can I use Domain Maker in an existing Laravel application?
- Yes, but avoid retrofitting your entire app directory, which tends to produce a half-migrated hybrid structure. Pilot the tool on one new bounded context, hand-review the generated output against your house standards, and only then decide whether to adopt, fork, or reject it. Back-fill legacy code only where there is a clear owner and a reason.
- Does Domain Maker actually enforce domain-driven design?
- No. It generates folders and boilerplate, not bounded-context discipline or review processes. That creates a DDD-in-a-box risk where teams gain false confidence that architecture has been addressed. Pair it with an explicit convention document and code review to get real value.
- How do I fork Domain Maker to support newer Laravel versions?
- Vendor a fork under an internal namespace rather than fighting the Composer resolver or holding your framework back. Put it in an internal repository with CI, stub regression tests, and tagged releases, and document onboarding around a reference domain. If the original constraints conflict with your target Laravel version, the fork is usually cheaper than waiting for upstream patches that will never come.
- What are the alternatives to Domain Maker for DDD-style scaffolding in Laravel?
- Common options include writing your own make:* stubs in-house, using other Laravel modular or DDD scaffolding packages, or sticking with plain Laravel generators plus a written convention guide. Evaluate each against your Laravel and PHP version matrix and your team's conventions. For many teams, in-house stubs are the lowest-risk long-term choice once a scaffolding tool is abandoned.
Weaver
How can I help you explore Laravel packages today?