- How do I install atefr/nova-money-field in Laravel Nova?
- Install the package with Composer using the atefr/nova-money-field package name. Laravel auto-discovery registers the service provider, and you can publish the configuration if the package provides config publishing. Confirm that Laravel Nova is already installed and that your Composer constraints allow the package's dependencies.
- Does this Nova money field support moneyphp/money v4?
- Version 1.5.1 adds support for moneyphp/money v4 according to the TPM assessment. That v4 upgrade requires PHP 7.4+ and changed amount handling in some contexts, so check whether your application still pins v3. Confirm in the package's composer.json whether v3 and v4 are supported simultaneously or whether v1.5.1 requires v4.
- What does cknow/laravel-money support mean for this package?
- Version 1.5.1 adds support for cknow/laravel-money, which can reduce duplication for teams already using that Laravel money package. The TPM assessment says this support is likely optional but should be confirmed because it could affect default behavior. Decide whether this package replaces, wraps, or complements cknow/laravel-money before adding both dependencies.
- Can I configure currency symbols and decimal precision in the Nova field?
- Yes. The package is described as a Nova money field with configurable currency symbols, decimal precision, and formatting. Use the published configuration or field options to keep prices and amounts consistent and readable across Nova admin panels, resources, and forms.
- Which Laravel and PHP versions does atefr/nova-money-field support?
- The TPM assessment does not list exact Laravel version constraints, so check the package's composer.json for supported Laravel and PHP ranges. It notes that moneyphp/money v4 requires PHP 7.4+, and the practical Laravel requirement may be higher depending on your application. Confirm compatibility before upgrading in production.
- Is this package a replacement for cknow/laravel-money or a wrapper around it?
- The package is a Laravel Nova money field, and after v1.5.1 it can interoperate with cknow/laravel-money. The TPM assessment says its positioning as an alternative, wrapper, or bridge is ambiguous. Run a small spike and decide whether to consolidate on one money abstraction in application code.
- How should I test money formatting and arithmetic after upgrading to v1.5.1?
- Create a branch, run composer why moneyphp/money and composer why cknow/laravel-money, and use a Composer dry-run to surface dependency conflicts. After upgrading, run unit and integration tests focused on money formatting, arithmetic, rounding, serialization, and currency handling. Pay special attention if Money objects cross the package's boundaries.
- Are there breaking changes in atefr/nova-money-field v1.5.1?
- The release is labeled v1.5.1 and adds dependency support rather than a documented public API break, according to the TPM assessment. However, the upstream moneyphp/money v4 upgrade can affect arithmetic, formatting, serialization, and rounding. Treat it as a dependency upgrade and validate it against semver expectations and your full test suite.
- How does this Nova money field handle money serialization and rounding?
- The package itself focuses on displaying and editing monetary values with currency symbols and decimal precision. Rounding, arithmetic, and serialization behavior depend heavily on the underlying money library, especially after moneyphp/money v4. Test how Money objects are serialized and rounded if they leak through the field or resource boundaries.
- What alternatives exist to atefr/nova-money-field for money fields in Laravel Nova?
- Alternatives include using cknow/laravel-money directly or building a custom Nova field around moneyphp/money. This package is positioned as a Nova-native money field with configurable symbols, precision, and formatting. Compare maintenance, Laravel and Nova version support, and whether you need interoperability with cknow/laravel-money.