Weave Code
Domain Bundle Laravel Package
open-solid/domain-bundle
A Laravel bundle for structuring domain-driven applications with SOLID-friendly building blocks, helping organize domain logic into clear, reusable components while keeping framework concerns separate from your core business model.
Symfony bundle for domain building blocks
Frequently asked questions about Domain Bundle
- What is open-solid/domain-bundle used for?
- It is described as a Symfony bundle for domain building blocks, intended to help structure domain-driven applications with SOLID-friendly primitives. The supplied blurb also calls it a Laravel bundle, but the package name and -bundle suffix point to Symfony vocabulary. Treat the exact feature set as unverified until you read the repository and composer.json. For Laravel teams, the key question is whether it is framework-agnostic or ships Symfony integration code.
- Is open-solid/domain-bundle a Laravel package or a Symfony bundle?
- The repository description says it is a Symfony bundle for domain building blocks. The supplied blurb calls it a Laravel bundle, which conflicts with the package name and the -bundle suffix. Do not assume Laravel support without checking composer.json and the source for Laravel service providers or Symfony Bundle classes. If it is Symfony-coupled, it belongs in infrastructure, not your Laravel domain layer.
- How do I install open-solid/domain-bundle with Composer?
- The TPM assessment gives the mechanical command as composer require open-solid/domain-bundle:^1.0. Pin the major version and commit your lock file. Before writing code, run composer why-not against your existing illuminate/* and symfony/* constraints. Because the release notes are empty, verify the package's composer.json requirements rather than relying on the tag.
- Does open-solid/domain-bundle support Laravel 10 or Laravel 11?
- There is no visible Laravel version support matrix in the provided release information. The package is described as a Symfony bundle, and the release body contains only an auto-generated compare link. You must inspect composer.json for illuminate/support or laravel/framework constraints, and check whether a CI matrix proves compatibility. If it requires Symfony components, adding it to a Laravel app introduces a parallel ecosystem to patch.
- Which PHP versions does open-solid/domain-bundle require?
- The PHP constraint is not visible from the release notes or the overview. The TPM assessment explicitly flags the php requirement as an unknown and notes that ^8.1 differs materially from ^7.4. Read composer.json before adopting. Also check whether the package's CI matrix tests the PHP versions you deploy.
- Is open-solid/domain-bundle framework-agnostic?
- The name and -bundle suffix suggest it may ship Symfony integration, so framework-agnosticism is not established. A true domain-layer library should keep entities, value objects, aggregates, domain events, and repository contracts free of framework types. Check for Symfony Bundle classes, service providers, facades, or Eloquent-specific base models. If any exist, treat exported types as infrastructure you must wrap.
- What changed between open-solid/domain-bundle v1.0.4 and v1.0.5?
- The v1.0.5 release body contains no prose, only an auto-generated compare link. No breaking changes, feature list, deprecation notices, CVE reference, or linked PRs are stated. For a patch release under semver the upgrade risk is low, but the behavioral diff is not triageable from the release alone. Review the compare link or repository commits if you need auditable change evidence.
- Is open-solid/domain-bundle safe for production and SOC 2 change management?
- The package is at v1.0.5 with patch-level semver discipline, which is a positive signal, but the opaque changelog is a concern for audited environments. SOC 2 and ISO 27001 change-management controls require evidence of what changed and who reviewed it. Verify contributor count, commit cadence over the last 12 months, green CI on the tag, license, and a security disclosure path. If those are missing, treat adoption as a supply-chain risk.
- How should I introduce open-solid/domain-bundle into an existing Laravel DDD codebase?
- Do not refactor existing Eloquent models onto the package. Introduce it in one bounded context, map existing entities into its primitives through a thin anti-corruption layer, and keep its types out of controllers, jobs, and serialized payloads. If the package is Laravel-coupled or Symfony-coupled, wrap it before it touches HTTP or persistence boundaries. A clean seam makes the migration additive and reversible.
- What are the alternatives to open-solid/domain-bundle for Laravel DDD?
- The assessment notes the package may duplicate capability you already have in-house, so first identify what it would replace. For Laravel teams, framework-agnostic DDD primitives or your own domain layer may be safer than a Symfony-oriented bundle. Compare against packages that explicitly declare Laravel support and publish a CI matrix. The decisive test is whether the dependency stays at the innermost layer without dragging framework concerns into your model.
Weaver
How can I help you explore Laravel packages today?