Weave Code
Core Bundle Laravel Package
elcodi/core-bundle
Core Bundle is part of Elcodi, an MIT-licensed suite of e-commerce components and bundles for Symfony. This package is read-only; use the main elcodi/elcodi repository for issues, questions, and pull requests.
[READ-ONLY] Subtree split of the Elcodi Core bundle
Frequently asked questions about Core Bundle
- Can I install elcodi/core-bundle in a Laravel application?
- You can add it to composer.json, but it is a Symfony bundle, not a Laravel package. Its service definitions, compiler passes, and configuration trees assume a Symfony kernel, and its legacy Symfony, Doctrine, and PSR constraints are likely to conflict with the Symfony 6/7 packages Laravel already pulls in. Composer resolution failure is the expected outcome, so treat installation as unsupported.
- Does elcodi/core-bundle support Laravel 10 or Laravel 11?
- No. elcodi/core-bundle is built for Symfony and is part of the Elcodi e-commerce suite; it exposes no Laravel service provider, facade, or framework-agnostic API. There is no declared Laravel version support, and the underlying Symfony 2.x-era components are not compatible with modern Laravel stacks. Use it as a reference, not a dependency.
- What is elcodi/core-bundle used for?
- It is the core Symfony bundle in Elcodi, an MIT-licensed e-commerce component and bundle suite. It provides kernel-registered DI service definitions, compiler passes, and configuration for commerce domain concepts such as cart and order state, currency and locale context, and pricing and tax abstractions. In a Laravel context its value is informational: a worked reference for modeling commerce behavior.
- Is elcodi/core-bundle a drop-in commerce package for Laravel?
- No. It is not a Laravel package and does not expose a PSR-only, framework-agnostic surface that can be dropped into a Laravel app. Laravel's container, HTTP kernel, event dispatcher, and Eloquent are adjacent to Symfony's but not substitutable. A real integration would require a partial Symfony kernel, a service boundary, or a concept port.
- Is elcodi/core-bundle still maintained?
- This repository is a read-only subtree split, so issues and pull requests are not handled here. The only contribution surface is the upstream elcodi/elcodi monorepo, and the codebase is Symfony 2.x-era. Treat the 0 stars and readme maturity as artifacts of the split, not as popularity evidence; the real maintenance question is whether upstream is active and whether you are willing to own a fork.
- What PHP versions does elcodi/core-bundle require?
- Expect PHP 5.x-era idioms and legacy dependencies rather than a modern PHP 8.1+ baseline. Dynamic properties, removed functions, and type-juggling assumptions can pass static review and fail at runtime on current PHP. Check any specific release's composer.json, but assume a PHP version gap against a modern Laravel target.
- How do I report a bug or contribute a fix to elcodi/core-bundle?
- Do not open pull requests or issues in this repository; it is read-only by design. Use the main elcodi/elcodi package for issues, questions, and pull requests. If you need a fix for a Laravel integration, plan for a fork you maintain or re-express the relevant behavior in your own code.
- What are the alternatives to using elcodi/core-bundle with Laravel?
- First name the capability you need: checkout state machine, currency and tax handling, catalog modeling, or event and context plumbing. Then check for a Laravel-native package that covers that exact slice, or build the narrow domain model in-house under app/Domain. Running Elcodi as a standalone Symfony service over HTTP or queues is architecturally possible, but it is a platform decision with a doubled runtime surface.
- How do I port and test Elcodi Core Bundle concepts in Laravel?
- Inventory CoreBundle's service definitions and sibling components to enumerate domain concepts and invariants such as currency context, locale resolution, pricing and tax rules, and entity lifecycle hooks. Re-express them as Laravel-native value objects, DTOs, repositories or Eloquent models, and events and listeners, mapping Elcodi event names one-for-one for traceability. Write characterization tests around the invariants you care about before and after the port, especially cart and order state transitions, currency and locale resolution, and pricing and tax rules. Package the result internally as a versioned Composer package rather than installing the Symfony bundle.
- What production risks should I consider before depending on elcodi/core-bundle?
- The main risks are framework lock-in, Composer resolution conflicts with modern Symfony packages, and PHP 5.x code failing on PHP 8.1+. The read-only distribution means fixes become a fork you own, and there is no upstream disclosure process you control. If you choose a separate-service boundary, also account for operating and securing an additional Symfony runtime.
Weaver
How can I help you explore Laravel packages today?