- Does symfgenus/money-bundle work with Laravel?
- No. It is a Symfony2 bundle that registers services into Symfony's kernel, DI container and configuration tree, and Laravel has none of those. There is no service provider, no facade, no publishable config and no package:discover support, so Composer will install files that Laravel never boots. For a Laravel application the bundle does not fit architecturally at all.
- How do I install symfgenus/money-bundle?
- You would need to add a VCS repository entry pointing at the GitHub fork, because the Composer name does not line up with the repository and it is not reliably available on Packagist. Its Symfony2 constraints also conflict with PHP 8.1+ and modern Composer resolution, so installs typically fail before any code runs. It is not a recommended installation path for any current project.
- What should I use instead of symfgenus/money-bundle in Laravel?
- Use moneyphp/money (v4.x) directly and declare ext-bcmath or ext-gmp plus ext-intl in composer.json. moneyphp/money is the actively maintained successor to the abandoned mathiasverraes/money library this bundle wraps. Pair it with a custom Eloquent cast so domain code never handles raw integers or floats.
- Which PHP and Symfony versions does this bundle support?
- It targets Symfony2, which reached end of life years ago and receives no security fixes. Its constraints predate typed properties and modern PHP, so expect deprecated syntax and dependency conflicts on PHP 8.1 and above. Running it on a supported runtime is not viable.
- Is symfgenus/money-bundle safe to use in production?
- The risk is high. There is no maintainer, no security feed, no CI, zero stars and zero dependents, so any defect you hit becomes yours to fix. Monetary code fails silently through rounding drift, float coercion and mixed currencies rather than throwing, which makes an unmaintained wrapper especially dangerous.
- Why does the Composer name differ from the GitHub repository name?
- The package is listed as symfgenus/money-bundle while the repository is hanishsingla/TbbcMoneyBundle, which is a fork signal. You should verify the composer.json name, branch lineage and divergence from upstream before trusting the artifact. Unverified provenance plus no release cadence is a strong argument for not adopting it.
- How should I store monetary values in a Laravel database?
- Store the amount as integer minor units in a BIGINT column alongside an ISO 4217 CHAR(3) currency column, and never use FLOAT or DOUBLE. A bare DECIMAL without a currency column is also a trap because it invites mixing currencies. Map the two columns to a Money object with an Eloquent custom cast so the rest of the codebase only sees value objects.
- What rounding and precision rules should money handling follow?
- Respect ISO 4217 minor units and per-currency exponents rather than assuming two decimal places. Use bcmath or gmp for arithmetic and apply an explicit rounding mode such as banker's rounding where finance requires it. Decide up front whether tax is stored inclusive or exclusive and keep allocation remainders deterministic when splitting amounts.
- How do I test money handling in a Laravel application?
- Unit test the Eloquent cast round-trip so integers and Money objects survive save and reload unchanged. Cover allocation and split remainders, mixed-currency exceptions and locale formatting through intl's NumberFormatter. Property-based or fuzz tests are worth adding because rounding drift only shows up across many operations.
- What is Fowler's Money pattern and why does it matter here?
- The pattern models an amount in minor units paired with a Currency as an immutable value object, which prevents accidental float math and currency mixing. That idea is durable and worth adopting; the Symfony2 bundle that wires it up is not. Implement the pattern with moneyphp/money and your own Laravel integration layer instead of this package.