Weave Code
Customer Bundle Laravel Package
monofony/customer-bundle
Monofony Customer Bundle provides customer management for Symfony e-commerce applications, including customer entities, profiles, repositories, factories, and related services for integrating account, registration, and address workflows into a storefront.
Customers management for Symfony projects.
Frequently asked questions about Customer Bundle
- Is monofony/customer-bundle a Laravel package?
- No. It is a Symfony bundle from the Monofony e-commerce stack, shipped with a DependencyInjection extension, Doctrine ORM mappings and configuration trees consumed through config/bundles.php. None of that wiring executes under Laravel's kernel, so Composer may resolve the dependency but the bundle will never boot. In a Laravel codebase the realistic option is reimplementing the Customer and Address model in Eloquent rather than installing it.
- How do I install monofony/customer-bundle in a Symfony application?
- Install it with Composer, then register CustomerBundle in config/bundles.php and import its configuration tree into your Symfony config. You also need Doctrine ORM, Symfony Security and the EventDispatcher available, plus a firewall entry that uses the bundle's customer resolver for authentication. The bundle's dependency injection extension then provides the customer factory, repository and manager services automatically.
- Does monofony/customer-bundle work with Symfony 6 or Symfony 7?
- Not without patching. The bundle is a Symfony 4.4 and 5.x-era artifact, and version 1.10.0 did not bump any Symfony constraint or migrate its DI or security configuration. Expect to deal with TreeBuilder and Configuration signature changes, annotation-to-attribute mapping, autowiring adjustments and the PasswordEncoder to PasswordHasher rename. Budget real engineering time before assuming a drop-in upgrade.
- What PHP versions does monofony/customer-bundle 1.10.0 support?
- Version 1.10.0 adds PHP 8 support, but that is a runtime floor change only. In a bundle of this vintage it usually means PHP 8.0 rather than 8.1, 8.2 or 8.3, so verify it against your actual runtime before relying on it. No Doctrine, DBAL or Symfony modernization accompanied that change.
- Is monofony/customer-bundle still actively maintained?
- Treat it as low maintenance. It is a read-only split of the Monofony monorepo, so pull requests are not accepted here and the canonical source lives elsewhere, and there is roughly one star, no dependents and no visible release cadence. A single PHP 8 compatibility commit after a long quiet period signals that someone unblocked the build, not that the project is alive. If you fork it, that fork becomes your own maintenance burden.
- What entities and services does the bundle actually provide?
- It ships ready-made Customer and Address entities with Doctrine mappings, plus a configurable customer factory, repository and manager. The Customer model covers email, first and last name, phone, gender and birthday. It also wires customers into Symfony Security so registration, login and profile flows work out of the box, and it exposes interfaces such as CustomerInterface for extension.
- What should I use instead of this bundle for customer management in Laravel?
- If your requirement is simply a customer profile attached to an existing account, Laravel's default users table plus a customer_profiles table is a two to three day build and the bundle is irrelevant. If you need a fuller e-commerce customer domain, model it in Eloquent with your own repository and factory classes rather than porting Symfony resource factories. Inside Symfony or Sylius, use it only as a reference implementation or for a legacy Monofony-style application.
- Is it safe to use monofony/customer-bundle in production?
- There is moderate security exposure because the bundle includes authentication surfaces: login and logout, a customer resolver and password handling. Unmaintained authentication code is the riskiest kind of unmaintained code, and a PHP version compatibility patch is not a security maintenance signal. If you depend on it, you own the CVE triage for that surface yourself.
- Can I extend the Customer entity with custom fields and business rules?
- Yes, the architecture is designed for it. You can subclass or replace the Customer and Address entities, override the factory and repository services through the bundle's configuration, and add your own business rules in custom services. Because the canonical development happens in the Monofony monorepo, plan to carry those customizations in your application or a fork rather than upstream.
- What license does monofony/customer-bundle use, and can I fork it?
- It is released under the MIT license, so there is no licensing risk and forking is permitted. The practical concern is not legal but operational: upstream pull requests are not accepted in this split repository, so any fork you create is yours to patch and maintain. Adopting it is better framed as mining it for design patterns than taking on a vendor dependency.
Weaver
How can I help you explore Laravel packages today?