Weave Code
Core Bundle Laravel Package
sylius/core-bundle
Sylius CoreBundle delivers the foundational domain models and services behind the Sylius e-commerce platform, covering products, orders, customers, payments, shipments, promotions, and taxes. It provides reusable PHP/Symfony components for building flexible online stores.
[READ-ONLY] Subtree split of the Sylius core - please see "Sylius" repository.
Frequently asked questions about Core Bundle
- Is sylius/core-bundle a Laravel package?
- No. sylius/core-bundle is a Symfony bundle that forms the foundational wiring layer of the Sylius e-commerce platform. It relies on Symfony bundle registration, dependency injection, Doctrine mappings, and the Symfony event dispatcher, none of which map to Laravel's package model or Eloquent ORM. For Laravel projects it should be treated as out of scope rather than as a Composer package to install.
- Can I install sylius/core-bundle in a Laravel application with Composer?
- Composer may resolve the package, but installation is not a supported Laravel consumption path. The bundle expects Kernel-level registration, Doctrine persistence, Symfony forms, and Symfony's container and event model, and Eloquent has no path to its Doctrine-mapped resources. Native integration feasibility is effectively zero; the viable pattern is running Sylius as a separate Symfony service and integrating over HTTP or a message bus.
- What is the difference between sylius/core-bundle and sylius/sylius?
- sylius/core-bundle is a read-only subtree split of the Sylius/Sylius monorepo, published so Composer can resolve the component transitively. It is not the supported entry point for adopting Sylius, and issues, pull requests, and release decisions live upstream in sylius/sylius. If you are building a Sylius application, declare sylius/sylius or the individual sylius/* components instead of depending on the split.
- Which Laravel versions does sylius/core-bundle support?
- None. The package has no Laravel version constraints because it is a Symfony bundle, not a Laravel package. Its compatibility is tied to Symfony, Doctrine, and the upstream Sylius release line. Laravel teams should evaluate Laravel-native commerce packages or a headless commerce API rather than looking for a version matrix here.
- How do I install sylius/core-bundle?
- In a Symfony or Sylius application you normally do not install it directly; it arrives as a transitive dependency of sylius/sylius and the Sylius feature bundles. Direct installation still requires a Symfony Kernel, bundle registration, Doctrine configuration, and the surrounding Sylius application skeleton. For a Laravel app there is no supported installation procedure.
- What are Laravel-friendly alternatives to Sylius CoreBundle for e-commerce?
- Laravel-native options include Lunar, Bagisto, Aimeos, and Vanilo, each with different trade-offs in maturity, licensing, and domain coverage. You can also integrate a headless commerce API or run Sylius as an isolated Symfony service behind an HTTP or message-bus boundary. The right choice depends on whether you are buying a commerce platform or composing commerce capabilities into an existing Laravel product.
- Can I use Sylius as a headless commerce backend for a Laravel frontend?
- Yes, but only through service isolation, not by installing sylius/core-bundle into Laravel. Deploy Sylius as its own Symfony application with its own database, then expose catalog, cart, checkout, and order operations over HTTP/JSON or a message bus. That is architecture work: you own API contracts, authentication, data synchronization, and deployment. It is a legitimate pattern, but it is not a package install and should be scoped as a separate service.
- Why does sylius/core-bundle have so few stars and dependents?
- Those metrics measure the wrong thing for a read-only subtree split. The repository exists so Composer can resolve Sylius components transitively; nobody is expected to depend on it directly, and development happens in the Sylius/Sylius monorepo. Judge the platform by Sylius upstream adoption, release cadence, and your team's Symfony depth, not by this split's independent signal.
- How do I customize or extend Sylius CoreBundle?
- Customization follows standard Symfony bundle conventions: service decoration, container configuration, compiler passes, Doctrine mapping overrides, and Sylius Resource, Grid, and StateMachine configuration models. Fixtures and migrations are also part of the extension surface. This requires production Symfony depth, including DI container compilation and Doctrine mapping, which is why it is a poor fit for Laravel teams.
- What technical requirements and risks come with sylius/core-bundle?
- It requires a Symfony Kernel, Doctrine persistence, Symfony forms, the event dispatcher, and state machines for order and payment workflows, and it typically pulls a broad sylius/* graph plus Doctrine, Symfony, API Platform, and Messenger. Versioning inherits upstream Sylius tags with no independent cadence, so patch availability depends on Sylius release process. Forking the split is not a viable patching strategy because a fork is unmergeable upstream, and reversing the decision later is a commerce-domain rewrite rather than a library swap.
Weaver
How can I help you explore Laravel packages today?