remove backwards compatible code, use npm versioning instead #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed code for backwards compatibility. If you publish this as 0.2.0, code that needs to be backwards compatible can still use 0.1.0. Let npm and package.json take care of the rest :)
Note that I also changed the return value to an empty object instead of returning null if no info can be found for a particular coin.
I aim to add more support for default ports (could also have default rpc port) and also for network magic numbers.