Weave Code
Shared Kernel Laravel Package
lin3s/shared-kernel
A lightweight PHP shared kernel offering reusable DDD building blocks such as value objects, identifiers, aggregates, domain events, and specifications for consistent modeling across bounded contexts.
Lin3S Shared Kernel provides reusable Domain-Driven Design primitives for PHP applications, helping teams model a consistent shared kernel without duplicating common domain concepts. It offers lightweight base types and contracts for building expressive, framework-agnostic domain models.
- Value Objects and identifiers for immutable, type-safe domain values
- Entities and Aggregate Roots with identity-based equality
- Domain Events and event collection support
- Collections and common domain exceptions
- Framework-agnostic PHP with Composer autoloading
Frequently asked questions about Shared Kernel
- What is lin3s/shared-kernel used for in Laravel?
- It is a lightweight PHP shared kernel intended for domain-driven and CQRS-based applications. It groups reusable building blocks such as identifiers, value objects, aggregates, domain events, and base exceptions so bounded contexts can avoid duplicated infrastructure code. In a Laravel app it would be used as a framework-agnostic domain layer dependency, not as a Laravel package with framework features.
- Is lin3s/shared-kernel compatible with Laravel 10 or Laravel 11?
- Probably not without changes. The last release was in September 2018, which suggests PHP 7.x-era Composer constraints and likely conflicts with Laravel 10, Laravel 11, and PHP 8.2+. You should test installation in a disposable branch and audit PHP compatibility before relying on it.
- How do I install lin3s/shared-kernel with Composer?
- Install it with composer require lin3s/shared-kernel only after checking its composer.json constraints. There is no documented Laravel service provider or configuration step to publish. In most cases you will autoload the classes and wire them manually into your domain and application layers.
- Does lin3s/shared-kernel provide a Laravel service provider or facade?
- You should not assume one. The assessment found no Laravel service provider, facade, config, or migration surface, and the package is described as framework-agnostic. Any Laravel integration would be manual autoloading and wiring rather than package-provided bootstrapping.
- What DDD and CQRS primitives does lin3s/shared-kernel include?
- The package is described as offering identifiers, value objects, aggregates, domain events, and base exceptions. These are generic DDD and CQRS primitives intended to be shared across bounded contexts. You still need to audit the actual namespaces and public API to confirm whether they are generic or LIN3S-specific.
- Is lin3s/shared-kernel still maintained?
- Maintenance signals are poor. It had 1 GitHub star, 0 dependents, and a last release in September 2018 at the time of assessment, so upstream fixes are unlikely. Treat it as legacy reference code rather than an actively maintained dependency.
- Can I use lin3s/shared-kernel in production?
- Production use is high risk without an internal fork and ownership plan. The package is unmaintained, likely has old PHP constraints, and may not receive security or compatibility fixes. If you need its primitives, copying or forking the small useful subset into an internal namespace is usually safer than taking a long-lived Composer dependency.
- Should I use lin3s/shared-kernel or copy its classes into my app?
- Copying is often the better choice for a small shared kernel. The assessment recommends extracting only the primitives you need, auditing them, and owning them internally. Taking the package as-is spreads unmaintained domain semantics and hidden assumptions across your codebase.
- What PHP version does lin3s/shared-kernel require?
- The exact constraints are not confirmed in the provided context, but the 2018 release date strongly suggests PHP 7.x-era requirements. You must inspect composer.json and run a compatibility check against PHP 8.2+ and your Laravel version. Do not assume it installs cleanly on modern PHP.
- What are alternatives to lin3s/shared-kernel for Laravel DDD?
- For Laravel DDD, consider maintained libraries or internal primitives rather than an abandoned shared kernel. You can implement identifiers, value objects, and domain events directly in a small internal package under your own namespace. If you want Composer alternatives, evaluate actively maintained DDD packages with recent releases and Laravel compatibility evidence.
Weaver
How can I help you explore Laravel packages today?