accounting, currency.js, dinero.js, and numeral are JavaScript libraries designed to handle number formatting and currency operations, but they serve different architectural needs. accounting and numeral focus primarily on string formatting for display, with numeral also offering basic math operations that are not safe for financial calculations. currency.js and dinero.js are built specifically for money, using integer-based math to avoid floating-point errors, with dinero.js offering a more functional and immutable approach. Choosing the right tool depends on whether you need simple display formatting or robust, error-free financial logic.
When building financial features or data dashboards, how you handle numbers matters. Using native JavaScript numbers for money is risky due to floating-point errors (e.g., 0.1 + 0.2 !== 0.3). The packages accounting, currency.js, dinero.js, and numeral attempt to solve this, but they take very different approaches. Some focus only on how the number looks, while others focus on how the math works. Let's compare them based on real engineering needs.
Not all libraries are built for the same job. accounting and numeral are primarily formatters. They take a number and turn it into a string. currency.js and dinero.js are calculation engines that also format. They wrap the value in an object to keep math safe.
accounting is purely for formatting. It does not store state or handle math safely.
// accounting: Format only
import accounting from 'accounting';
const display = accounting.formatMoney(1234.56);
// "$1,234.56"
currency.js wraps the value so you can chain math and formatting.
// currency.js: Math and Format
import currency from 'currency.js';
const val = currency(1234.56);
const display = val.format();
// "$1,234.56"
dinero.js uses integers (cents) to ensure precision during math.
// dinero.js: Math and Format (Integer based)
import Dinero from 'dinero.js';
const val = Dinero({ amount: 123456, currency: 'USD' });
const display = val.toFormat();
// "$1,234.56"
numeral is a general number formatter that supports many types (bytes, percentages).
// numeral: Format only (General)
import numeral from 'numeral';
const display = numeral(1234.56).format('$0,0.00');
// "$1,234.56"
This is the most critical architectural decision. JavaScript numbers are floating-point, which causes rounding errors. dinero.js and currency.js solve this differently.
accounting has no math methods. You must use native JS math, which is unsafe for money.
// accounting: No built-in math
// You must do this manually (UNSAFE for money)
const total = 10.10 + 20.20;
const display = accounting.formatMoney(total);
currency.js handles the conversion internally. You pass decimals, it stores them safely.
// currency.js: Safe math with decimals
const total = currency(10.10).add(20.20);
console.log(total.value); // 30.30
dinero.js requires you to pass integers (cents). This forces precision at the input stage.
// dinero.js: Safe math with integers
const d1 = Dinero({ amount: 1010, currency: 'USD' });
const d2 = Dinero({ amount: 2020, currency: 'USD' });
const total = d1.add(d2);
console.log(total.getAmount()); // 3030
numeral supports math operations, but uses native floating-point numbers.
// numeral: Unsafe math (Floating point)
const total = numeral(10.10).add(20.20);
console.log(total.value()); // May result in 30.2999999...
Formatting needs vary by region. Some libraries handle localization better than others.
accounting allows custom symbols and separators via options.
// accounting: Custom options
accounting.formatMoney(1234, "€", 2, ".", ",");
// "€1.234,00"
currency.js supports locale options for formatting output.
// currency.js: Locale support
currency(1234.56, { locale: 'de-DE' }).format();
// "1.234,56 €"
dinero.js relies on external libraries (like Intl) for complex localization in V1.
// dinero.js: Basic format
Dinero({ amount: 123456, currency: 'USD' }).toFormat();
// "$1,234.56" (Limited locale support in V1)
numeral uses token-based formatting which is very flexible but manual.
// numeral: Token based
numeral(1234.56).format('0,0.00 $');
// "1,234.56 $"
Architectural decisions must account for the library's lifespan. Using unmaintained code introduces security and compatibility risks.
accounting is stable but effectively inactive. It works for simple tasks but won't get new features.
// accounting: Stable but legacy
// No recent updates, but API is unlikely to break
import accounting from 'accounting';
currency.js is actively maintained and lightweight.
// currency.js: Active maintenance
// Regular updates and modern JS support
import currency from 'currency.js';
dinero.js V1 is in maintenance mode while V2 is in development.
// dinero.js: Transitioning
// V1 is stable, V2 is a major rewrite (check docs for V2 status)
import Dinero from 'dinero.js';
numeral is unmaintained. The original repo is archived.
// numeral: UNMAINTAINED
// Do not use in new projects. Look for forks or alternatives
import numeral from 'numeral';
| Feature | accounting | currency.js | dinero.js | numeral |
|---|---|---|---|---|
| Primary Use | Currency Formatting | Currency Math & Format | Financial Precision | General Number Format |
| Math Safety | ❌ (Native JS) | ✅ (Internal handling) | ✅ (Integer based) | ❌ (Floating point) |
| Immutability | ❌ | ✅ | ✅ | ❌ |
| Maintenance | ⚠️ Legacy | ✅ Active | ⚠️ V1 Maintenance | ❌ Unmaintained |
| Learning Curve | Low | Low | High | Low |
For Financial Logic: Use dinero.js if you need strict precision and can handle the integer-based API. It is the safest choice for banking, accounting, or e-commerce backends. Use currency.js if you need a simpler API for frontend carts or displays where you still want math safety without the verbosity of dinero.js.
For Display Only: Use accounting if you are maintaining a legacy system that already uses it. For new projects requiring only formatting, consider using the native Intl.NumberFormat API instead of adding a dependency.
Avoid: Do not use numeral for currency. It is unmaintained and unsafe for money math. Do not use accounting or numeral for any calculation logic involving money.
Modern Alternative: For simple formatting in new projects, the native browser API is often enough:
// Native Intl API (No dependency)
new Intl.NumberFormat('en-US', {
style: 'currency',
currency: 'USD'
}).format(1234.56);
// "$1,234.56"
Avoid numeral for new projects as the original repository is no longer maintained. While it offers flexible formatting for general numbers (percentages, bytes, etc.), it uses floating-point math which is unsafe for currency. Only consider it for non-financial display formatting if you accept the risk of using unmaintained software.
Choose currency.js if you want a balance between ease of use and safety for currency math. It handles floating-point errors internally and offers a chainable API that is easier to learn than dinero.js. It is ideal for e-commerce carts or simple payment flows where you need both formatting and addition.
Choose dinero.js if you are building a financial application where precision and immutability are critical. It forces you to work with integers (cents) to prevent rounding errors and provides a robust API for allocations and comparisons. It has a steeper learning curve but offers the highest safety for serious money handling.
Choose accounting if you need a lightweight, zero-dependency solution strictly for formatting currency strings in legacy projects. It is stable and simple, but lacks modern features like immutable objects or safe math operations. Do not use it for calculating totals or handling complex financial logic.
A javascript library for formatting and manipulating numbers.
#CDNJS
develop branch. All pull requests must include the appropriate tests.Fork the library
Run npm install to install dependencies
Create a new branch from develop
Add your tests to the files in /tests
To test your tests, run grunt
When all your tests are passing, run grunt dist to compile and minify all files
Submit a pull request to the develop branch.
Formats now exist in their own files and act more or less as plugins. Check out the bytes format for an example of how to create one.
When naming locale files use the ISO 639-1 language codes supplemented by ISO 3166-1 country codes when necessary.
See the english unit tests for an example.
Bug fix: Multi letter currency symbols and spacing
Added: Formatting of numbers with leading zeros
New format: Basic Point
Option: Added scalePercentBy100 (default: true) option to turn on/off scaling percentages
Bug fix: Incorrect abbreviations for values rounded up #187
Bug fix: Signed currency is inconsistent #89
Bug fix: Updated module definitions
Bug fix: Fixed regression for webpack/browserify/rollup
2.0.0 brings a lot of breaking changes and a reorganization of the repo, but also simplifies the api as well as the creating of custom formats.
Breaking change / Feature: All formats are now separate files. This makes it easy to create custom formats, and will also allow for custom builds with only certain formats. (Note: The built numeral.js still contains all formats in the repo).
Breaking change / Feature: All formats and locales are now loaded using numeral.register(type, name, {})
Breaking change: All language now renamed to locale and standardized to all lowercase filenames
Breaking change: The locale function no longer loads locales, it only sets the current locale
Breaking change: The unformat function has been removed numeral().unformat(string) and now happens on numeral init numeral(string)
Breaking change / Feature: Bytes are now formatted as: b (base 1000) and ib (base 1024)
Breaking change: numeral(NaN) is now treated the same as numeral(null) and no longer throws an error
Feature: Exponential format using e+ or e-
Bug fix: Update to floating point helpers (Note: Numeral does not fix JS floating point errors, but look to our tests to see that it covers quite a few cases.)
Bug fix: numeral converts strings to numbers
Bug fix: Null values return same as 0
Contained breaking changes, recommended to use 1.5.6
Bug fix: Switch bytes back to b and change iecBinary to ib, and calculate both using 1024 for backwards compatibility
Contained breaking changes, recommended to use 1.5.6
Tests: Changed all tests to use Mocha and Chai
Tests: Added browser tests for Chrome, Firefox, and IE using saucelabs
Added reset function to reset numeral to default options
Added nullFormat option
Update reduce polyfill
Added Binary bytes
Bug fix: Fixes problem with many optional decimals
Added currency symbol to optionally appear before negative sign / open paren
Added float precision math support
Added specification of abbreviation in thousands, millions, billions
Bug fix: Unformat should pass through if given a number
Added a mechanism to control rounding behaviour
Added languageData() for getting and setting language props at runtime
Bug fix: Make sure values aren't changed during formatting
Add defaultFormat(). numeral().format() uses the default to format if no string is provided
.unformat() returns 0 when passed no string
Added languages.js that contains all languages
Bug fix: Fix bug while unformatting ordinals
Add format option to always show signed value
Added ability to instantiate numeral with a string value of a number
Bug fix: Fix bug while unformatting ordinals
Bug fix: Throw error if language is not defined
Bug fix: Fix typo for trillion
Bug fix: remove ' from unformatting regex that was causing an error with fr-ch.js
Add zeroFormat() function that accepts a string for custom formating of zeros
Add valueOf() function
Chain functionality to language function
Make all minified files have the same .min.js filename ending
Bug fix: Bytes not formatting correctly
Add optional format for all decimals
Remove AMD module id. (This is encouraged by require.js to make the module more portable, and keep it from creating a global)
AMD define() compatibility.
Bug fix: Formatting some numbers results in the wrong value. Issue #21
Bug fix: Minor fix to unformatting parser
Add support for spaces before/after $, a, o, b in a format string
Bug fix: Fix unformat for languages that use '.' in ordinals
Bug fix: Fix round up floating numbers with no precision correctly.
Bug fix: Fix currency signs at the end in unformat
Add support for optional decimal places
Add support for appending currency symbol
Add support for humanized filesizes
Bug Fix: Fix unformatting for languages that use '.' as thousands delimiter
Changed language definition property 'money' to 'currency'
Bug fix: Fix unformatting non-negative abbreviations
Add language support
Update testing for to include languages
Add Tests
Bug fix: Fix difference returning negative values
Bug fix: Non negative numbers were displaying as negative when using parentheses
Add ordinal formatting using 'o' in the format
Add clone functionality
Added abbreviations for thousands and millions using 'a' in the format
Initial release
Numeral.js, while less complex, was inspired by and heavily borrowed from Moment.js
Numeral.js is freely distributable under the terms of the MIT license.
Copyright (c) 2012 Adam Draper
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.