Weave Code
Front Bundle Laravel Package
monofony/front-bundle
Monofony FrontBundle provides the customer-facing storefront layer for Monofony e-commerce applications, adding frontend routes, controllers, templates, and UI building blocks for product browsing, cart management, and checkout in Symfony.
Monofony front bundle.
Frequently asked questions about Front Bundle
- Is monofony/front-bundle a Laravel package?
- No. It is a Symfony bundle for the Monofony e-commerce framework, which itself is a Sylius derivative. It ships controllers, routes, Twig templates and form types wired through Symfony dependency injection, with no service provider, facade, Blade or Eloquent integration. In a Laravel codebase it is useful only as reference material for storefront UX and route patterns.
- How do I install monofony/front-bundle in a Symfony application?
- Require the package with Composer and register it in config/bundles.php after SyliusResourceBundle, SyliusGridBundle and MonofonyCoreBundle. Import the bundle routing last so your own local routes shadow it. On plain Sylius you will also need to align resource configuration and vendor any Monofony-specific base classes.
- Which Symfony versions does monofony/front-bundle support?
- Its constraints follow the Monofony and Sylius lineage, which historically tracked Symfony 4 and 5. Check the current branch composer.json and release tags against your host project's Symfony minor version before spending engineering time. Declared constraints are usually looser than what was actually tested, so run a throwaway dependency-resolution spike first.
- Can I use monofony/front-bundle with plain Sylius?
- Only partially. The bundle is designed for Monofony, so on plain Sylius you must align resource configuration in _sylius.yaml, map your entities to the bundle interfaces and vendor Monofony-specific base classes. Expect route shadowing and extra wiring compared with a native Monofony install.
- What does monofony/front-bundle actually provide?
- It supplies customer-facing controllers, route definitions, Twig templates, view models and form types for product browsing, cart management and checkout. It integrates with Monofony core services and Sylius resources so commerce logic stays reusable. A large share of the bundle is presentation you can override or reimplement.
- How do I override the Twig templates in monofony/front-bundle?
- Use the standard Symfony bundle override path, for example templates/bundles/MonofonyFrontBundle/, and copy the template you want to change there. Services and routes can be adjusted through the bundle configuration and extension points. This keeps your customizations outside vendor code during upgrades.
- Is monofony/front-bundle actively maintained?
- Project health is weak, with very little community validation, few dependents and no visible upgrade history. Check recent commits, release tags and issue responsiveness before adopting it. The MIT license gives legal freedom but no maintenance guarantee, so plan for the bus factor.
- What are the alternatives to monofony/front-bundle for Laravel?
- For Laravel, use a native commerce stack such as Lunar, Bagisto, Aimeos or a headless commerce API instead. Reimplement the storefront patterns, Twig layouts and route naming conventions rather than attempting a Composer install. There is no supported install path from this Symfony bundle into Laravel.
- What are the production risks of using monofony/front-bundle?
- Transitive pinning of Sylius components, Doctrine ORM and Twig may constrain your application's dependency graph. Coupling to Sylius internals is undocumented and can break silently on upgrades. A low-traffic package is also a supply-chain consideration, so fork and vendor it if you decide to proceed.
- How should I evaluate monofony/front-bundle before adopting it?
- Run a health gate first: recent commits, release tags and open-issue responsiveness, and stop if it fails. Then do a dependency-resolution spike against your target Symfony version on a throwaway branch. Inventory what the bundle provides and classify each piece as reusable, forkable or reimplement.
Weaver
How can I help you explore Laravel packages today?