lukechilds / coinlist

Comprehensive list of cryptocurrencies with metadata

coinlist

Comprehensive list of cryptocurrencies with metadata

List compiled from the coingecko.com API. Importable as a raw JSON file or an array with helper methods.

Install

yarn add coinlist

Usage

const coins = require('coinlist');

// coins is an array of coin objects:
[
  {
    id: 'bitcoin',
    symbol: 'BTC',
    name: 'Bitcoin'
  },
  {
    id: 'litecoin',
    symbol: 'LTC',
    name: 'Litecoin'
  },
  ...
]

// There is a useful helper method to search the array for a ticker symbol:
const btc = coins.get('BTC');
{
  id: 1,
  symbol: 'BTC',
  name: 'Bitcoin'
}

// Or get a specific property
coins.get('BTC', 'name');
// "Bitcoin"

// You can still use all the usual array methods on coins:
coins.map(coin => coin.name);
[
  'BTC',
  'LTC',
  ...
]

// Alternatively, you can load the raw JSON file:
const coinsJson = require('coinlist/src/coins.json');

API

coins

An array of coin objects.

coins.get(symbol, [property])

Returns a coin object.

Alternatively returns a coin property if the property argument is defined.

If the symbol cannot be found it will return undefined.

symbol

Type: string

The coin ticker symbol to search the array for.

property

Type: string

A single coin property to return instead of the entire coin object.

Valid properties are:

• id The CoinGecko API id.
• symbol The ticker symbol.
• name The readable name.

Update Coins

$ yarn update
Fetching latest currencies from the coingecko.com API...
Written 2306 coins to src/coins.json

Contributing

Pull requests are welcome to improve the code but please don't add currencies to coins.json directly. The JSON is automatically generated from the update script.

License

MIT © Luke Childs

coinlist's Issues

An in-range update of got is breaking the build 🚨

Version 8.3.2 of got was just published.

Branch	Build failing 🚨
Dependency	got
Current Version	8.3.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

got is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v8.3.2

Fix Got throwing an error in some cases when trying to pipe one got.stream into another one. 7ac705f

Commits

The new version differs by 2 commits.

• ad7b361 8.3.2
• 7ac705f fix Buffer.byteLength(req._header) throwing error (#490)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

dynamic retrival of cryptocurrency list

Replace the static list of cryptocurrencies (coins.json) with a retrival from
https://coinmarketcap.com/all/views/all/

;)

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴