Weave Code
Cart Bundle Laravel Package
leaphly/cart-bundle
Leaphly Cart Bundle is a Symfony bundle that adds reusable shopping cart functionality to PHP applications. It includes cart and line-item models, a cart manager, Doctrine persistence, and extension points for custom products, pricing, and checkout integration.
High quality cart for developers.
Frequently asked questions about Cart Bundle
- Can I use leaphly/cart-bundle in a Laravel application?
- No. It is a Symfony full-stack bundle that relies on DependencyInjection compiler passes, HttpKernel events, and optional FOSRestBundle, JMSSerializer, and Twig integration. Laravel has no bundle system or equivalent lifecycle, and its Symfony 2 era constraints will likely conflict with a modern Laravel lockfile. Treat it as reference material rather than a dependency.
- What is leaphly/cart-bundle used for?
- It is a Symfony bundle for flexible shopping-cart workflows, including cart and cart-item abstractions, pluggable cart providers and item resolvers, multiple item types and quantities, and Doctrine-compatible persistence. It was built to integrate with Symfony applications, not Laravel.
- Is leaphly/cart-bundle still maintained?
- Maintenance risk is high. It targets an EOL Symfony 2 era, has zero dependents and roughly 101 stars, and shows strong abandonment signals. Assume no upstream fixes, security patches, or PHP 8.x and Laravel 10/11 support; confirm composer constraints, CI status, coverage, and license in a spike.
- How do I install leaphly/cart-bundle?
- Historically you installed it with Composer in a Symfony 2 application and registered the bundle. On a modern Laravel project the install is likely to fail on PHP, Symfony, or Doctrine constraints. If you evaluate it, vendor the repository read-only or clone it for source review rather than adding it to your runtime dependencies.
- Does leaphly/cart-bundle support Laravel 10 or Laravel 11?
- No. The bundle is pinned to PHP 5.x era and Doctrine 2.x era APIs and has no supported version matrix with Laravel 10 or Laravel 11. Expect hard Composer conflicts on the first install attempt. A native Laravel implementation is the realistic path.
- What are alternatives to leaphly/cart-bundle for Laravel?
- Build natively with Eloquent models, Laravel events and queues, a state column with explicit transition guards or a package such as spatie/laravel-model-states, and pipeline calculators for line price, tax, and discounts. You can also compare maintained Laravel cart packages, but most focus on storage and line items rather than the order-state workflow. Assess multi-currency, tax, and promotion needs before choosing.
- How should I test a cart implementation inspired by Leaphly CartBundle?
- Test the state machine guards and transitions, item and price resolver contracts, quantity rules, event dispatch on cart mutation, and persistence boundaries. Use PHPUnit or Pest with an in-memory database and contract tests for calculators and resolvers. Add edge cases for multi-currency, tax, promotion stacking, and concurrent cart updates if those are in scope.
- What production concerns exist if I adopt leaphly/cart-bundle?
- Production risk is dominated by abandonment and EOL dependencies, with no expected security patches and no PHP 8.x or Laravel 10/11 support. Booting a second Symfony kernel inside Laravel is technically possible but operationally an anti-pattern: two containers, two event systems, duplicated configuration, and unclear transaction boundaries between Eloquent and Doctrine. Do not adopt it as a runtime dependency for a production Laravel application.
- Can I extract the cart domain model from leaphly/cart-bundle into Laravel?
- Yes, the domain architecture extracts cleanly. Harvest the cart aggregate, cart-item model, product or variant references, guarded cart to wishlist to ordered state machine, pluggable price and item resolvers, and mutation events. Map those to Eloquent tables, explicit transition guards, a CartCalculator pipeline, Laravel events, Form Requests, and API Resources. A realistic extraction spike is about one to three weeks of engineering and leaves you owning the code.
- What configuration does leaphly/cart-bundle require?
- Configuration is Symfony-specific: service definitions and compiler passes, a DependencyInjection extension, Doctrine ORM mappings, and optional FOSRestBundle, JMSSerializer, and Twig wiring for HTTP. There is no Laravel config publishing or service-provider equivalent. In Laravel you would reimplement configuration for cart providers, item resolvers, calculators, and persistence.
Weaver
How can I help you explore Laravel packages today?