A simple module for handling Vapory unit convertion.
npm install --save vapjs-unit
const unit = require('vapjs-unit');
var val1 = unit.toWei(249824778, 'vapor');
// result <BN ...> 249824778000000000000000000
var val2 = unit.fromWei('249824778000000000000000000', 'vapor');
// result '249824778'
A port from the web3.js
library, that just handles the unit convertion between the various types of Vapory currency units.
Note, the toWei
returns a BN instance while fromWei
always returns a string number.
vapjs-unit
uses the number-to-bn module to format all number values (hex or otherwise) into digestable BN.js number instances.
unitMap { unitName: singleUnitWeiValue, ... }
getValueOfUnit <Function (unit) : (BN)>
toWei <Function (value, unit) : (BN)>
fromWei <Function (value, unit) : (String)>
'wei': '1',
'kwei': '1000',
'Kwei': '1000',
'babbage': '1000',
'femtovapor': '1000',
'mwei': '1000000',
'Mwei': '1000000',
'lovelace': '1000000',
'picovapor': '1000000',
'gwei': '1000000000',
'Gwei': '1000000000',
'shannon': '1000000000',
'nanovapor': '1000000000',
'nano': '1000000000',
'szabo': '1000000000000',
'microvapor': '1000000000000',
'micro': '1000000000000',
'finney': '1000000000000000',
'millivapor': '1000000000000000',
'milli': '1000000000000000',
'vapor': '1000000000000000000',
'kvapor': '1000000000000000000000',
'grand': '1000000000000000000000',
'mvapor': '1000000000000000000000000',
'gvapor': '1000000000000000000000000000',
'tvapor': '1000000000000000000000000000000'
vapjs
has made a policy of using BN.js
accross all of our modules. Here are some reasons why:
- Lighter than alternatives (BigNumber.js)
- Faster than most alternatives, see benchmarks
- Used by the Vapory foundation across all
vaporyjs
repositories - Is already used by a critical JS dependency of many vapory packages, see package
elliptic
- Does not support decimals or floats (for greater precision), remember, the Vapory blockchain cannot and will not support float values or decimal numbers
Please help better the ecosystem by submitting issues and pull requests to default. We need all the help we can get to build the absolute best linting standards and utilities. We follow the AirBNB linting standard and the unix philosophy.
You'll find more detailed information on using vapjs-unit
and tailoring it to your needs in our guides:
- User guide - Usage, configuration, FAQ and complementary tools.
- Developer guide - Contributing to
vapjs-unit
, writing coverage and updates.
There is always a lot of work to do, and will have many rules to maintain. So please help out in any way that you can:
- Create, enhance, and debug vapjs rules (see our guide to "Working on rules").
- Improve documentation.
- Chime in on any open issue or pull request.
- Open new issues about your ideas for making
vapjs-unit
better, and pull requests to show us how your idea works. - Add new tests to absolutely anything.
- Create or contribute to ecosystem tools, like modules for encoding or contracts.
- Spread the word.
Please consult our Code of Conduct docs before helping out.
We communicate via issues and pull requests.
This project is licensed under the MIT license, Copyright (c) 2016 Nick Dodson. For more information see LICENSE.md.
The MIT License
Copyright (c) 2016 Nick Dodson. nickdodson.com
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.