Weave Code
Currency Fieldtype Laravel Package
builtnoble/currency-fieldtype
A currency fieldtype for Laravel/PHP projects that makes it easy to capture, format, and display monetary values consistently in forms and content, with a clean, developer-friendly setup for currency-aware fields.
A Statamic fieldtype for storing and displaying monetary values as locale-aware, precision-safe integer subunits.
Frequently asked questions about Currency Fieldtype
- What is builtnoble/currency-fieldtype used for?
- It is a Statamic fieldtype for capturing and displaying monetary values in Laravel applications. It is designed to store values as locale-aware, precision-safe integer subunits so currency fields stay consistent in forms and content. It fits best inside Statamic blueprints, not as a general-purpose money service.
- How do I install builtnoble/currency-fieldtype in a Laravel project?
- The expected path is Composer installation, typically composer require builtnoble/currency-fieldtype, followed by Statamic add-on registration and fieldtype configuration. Install it in a non-production environment first and confirm your Statamic, Laravel, and PHP constraints. Then add the fieldtype to one low-risk blueprint before rolling it out.
- Does this package work in a plain Laravel app without Statamic?
- No, it is a Statamic fieldtype add-on rather than a standalone Laravel currency formatting or validation library. For a plain Laravel or non-Statamic application, stack fit is low. You would be better served by a dedicated money/currency domain library and your own form input.
- Which Laravel, Statamic, and PHP versions does it support?
- The provided assessment does not establish official runtime compatibility boundaries, so you should confirm supported Statamic, Laravel, and PHP versions before adoption. The v1.0.1 testbench bump is development-only unless runtime constraints changed elsewhere. Pin Composer constraints and verify against your application versions.
- How are monetary values stored by this fieldtype?
- The package is described as storing monetary values as integer subunits, which helps avoid floating-point precision issues. You should still review the stored data format and reporting/export behavior in your own content model. Confirm the exact field configuration and output expectations during staging.
- Does it support multiple currencies and locale-specific formatting?
- Locale-aware formatting is a core part of the package description, so display can adapt to locale settings. Multi-currency support is not confirmed in the provided context, so test currency switching and formatting explicitly. Also validate null, zero, and negative value handling for your use case.
- Can I use this fieldtype for billing, tax, pricing, or FX logic?
- No, it should not be treated as the source of truth for pricing, billing, tax, or foreign-exchange calculations. Those concerns belong in application or domain code with proper money handling. Use the fieldtype only for CMS-managed currency input and display.
- How should I test and roll out the fieldtype on existing content?
- Start in a non-production environment and validate add-on registration, input, storage, rendering, validation, localization, and empty states. Apply it to one low-risk content model and review stored data plus reporting/export behavior. Backfill or validate existing entries before broad rollout to avoid data-integrity issues.
- Is v1.0.1 safe to upgrade, and what support/license should I expect?
- v1.0.1 appears to be a maintenance-only patch that updates a dev/test dependency, CI, and documentation, with no evident runtime feature or breaking change. Treat release notes as evidence of maintenance, not proof of full compatibility, so pin versions and test. License terms and support model should be confirmed from the repository; unless commercial support is confirmed, assume self-support.
- When should I avoid builtnoble/currency-fieldtype, and what are the alternatives?
- Avoid it if you are not using Statamic or if you need a full money/currency domain library for billing, tax, or FX. It is also a poor fit when you need guaranteed multi-currency behavior that has not been validated for your stack. Alternatives are a dedicated money library plus a custom Laravel form input, or a different Statamic currency add-on that matches your version and support requirements.
Weaver
How can I help you explore Laravel packages today?