Weave Code
Core Bundle Laravel Package
monofony/core-bundle
Core bundle for Monofony, the Symfony-based e-commerce framework. It packages shared services, configuration, and foundational components used across Monofony applications, simplifying the setup of store features, resources, and common infrastructure within Symfony projects.
At a glance
Frequently asked questions about Core Bundle
- Is monofony/core-bundle compatible with Laravel?
- No. It is a Symfony full-stack bundle that assumes Symfony dependency injection, Doctrine ORM, Twig, and the Sylius resource and state-machine stack. It ships no Laravel service provider, facade, Eloquent model, or publishable Laravel config, so the Laravel package catalogue framing should not be read as compatibility.
- What is Monofony CoreBundle used for?
- It is the foundational bundle of the Monofony e-commerce framework, a Symfony-based storefront stack. It wires common services and configuration and provides base controllers, entities, repository abstractions, and integration points for Sylius components. Application bundles build business logic on top of it instead of repeating boilerplate.
- How do I install monofony/core-bundle?
- You install it with Composer as monofony/core-bundle inside a Symfony application that already uses Doctrine and the Sylius bundles it depends on. The first install is the most likely failure point because the bundle pins specific Symfony and Doctrine versions alongside sylius/resource-bundle, sylius/grid-bundle, sylius/fixtures-bundle, and stof/doctrine-extensions-bundle. Resolve those constraints against your existing dependency graph before adding it to a Laravel or mixed codebase, where it has no place.
- Which Symfony, Doctrine, and Sylius versions does it require?
- The exact pins live in the composer.json of the tag you are evaluating, and the bundle expects Symfony DI, Doctrine ORM, Twig, and Sylius resource and state-machine components. Because it also pulls Sylius resource, grid, and fixtures bundles plus stof/doctrine-extensions-bundle, version collisions are the most likely install problem. Check the current tag's constraints against your lock file rather than assuming broad compatibility.
- Can I bridge monofony/core-bundle into a Laravel app?
- A bridge translating Symfony services and Doctrine entities into Laravel-native constructs is technically possible but high effort and brittle, because it fights the idioms of both frameworks and is the path most likely to be abandoned. A sidecar Symfony service behind an API or queue boundary is more feasible but duplicates auth, sessions, and data ownership and adds a second runtime to operate. For a Laravel team the realistic default is to treat the bundle as reference architecture and reimplement the domain concepts natively.
- Is Monofony CoreBundle actively maintained?
- The adoption signals in this evaluation are weak: 2 stars, 0 dependents, and a composite score of 0.04. That does not prove the project is dead, but it means there is no community answer base, no Stack Overflow coverage, and no third-party confidence signal. Check the commit cadence over the last 12 months and who maintains it before any production commitment, because with zero dependents your team becomes the de facto maintainer.
- What are the alternatives to Monofony CoreBundle for Laravel e-commerce?
- If you need commerce in Laravel, benchmark maintained Laravel-native packages such as Lunar, Aimeos, or Bagisto before considering a Symfony sidecar. Those carry ecosystem support that this bundle does not. Monofony CoreBundle only makes sense when the target application is already Symfony/Sylius and the domain scope matches a real e-commerce roadmap need.
- How should I test a Monofony CoreBundle integration?
- Test it inside a Symfony kernel where dependency injection compilation, Doctrine mapping, resource configuration, and Twig rendering can actually be exercised. There is no Laravel testing story here, so any Laravel-side test would only validate a bridge or sidecar contract, not the bundle itself. Start with a throwaway Symfony install that resolves the pinned Sylius and Doctrine dependencies before touching production code.
- What are the production risks of depending on monofony/core-bundle?
- The risks stack: near-zero external adoption, pinned Symfony/Doctrine/Sylius dependencies that can collide with your graph, and ownership risk because no dependents exist. There is also domain-fit risk, since this is an e-commerce core and solves nothing if your product need is generic. The one clean signal is the MIT license, which means no procurement friction and freedom to fork if you accept the maintenance burden.
- How do I exit or fork Monofony CoreBundle later?
- MIT licensing lets you fork and own the code, but the exit cost depends on how deeply you adopted Symfony conventions such as DI aliasing, YAML resource configuration, Doctrine resolve_target_entities, and Twig-era service ids. If you used it as reference architecture and reimplemented concepts in Laravel, exit cost is low. If you built a production sidecar on it, plan for fork-and-own or rewrite, and isolate it behind a versioned API contract from day one.
Weaver
How can I help you explore Laravel packages today?