The base62.js from base62

Converting base 62 to base 16

I'm trying to convert base 62 to base 16. When I do the following..

Base62.decode('4u8LPK581OHn7kRqRqP9ks').toString(16)

I get 93669fd54as300000000000000000000. I'm expecting A12D08BC6D93BC4E8EA847434C960416. You can see a php based converter here http://convertxy.com/index.php/numberbases/ return the correct value.

Is the difference due to JS using scientific notation for these large numbers? In other words, Base62.decode('4u8LPK581OHn7kRqRqP9ks') returns 1.9592937146177773e+38. Does that munge the conversion to base 16 via toString(16)?

Thanks.

Upgrade balanced-match to version 1.0.0

Libraries.io has found that there is a newer version of balanced-match that this project depends on.

More info: https://libraries.io/npm/balanced-match/1.0.0

Upgrade growl to version 1.10.0

Libraries.io has found that there is a newer version of growl that this project depends on.

More info: https://libraries.io/npm/growl/1.10.0

Upgrade diff to version 3.3.0

Libraries.io has found that there is a newer version of diff that this project depends on.

More info: https://libraries.io/npm/diff/3.3.0

Upgrade supports-color to version 4.1.0

Libraries.io has found that there is a newer version of supports-color that this project depends on.

More info: https://libraries.io/npm/supports-color/4.1.0

doesnt round trip even 10 places

var Base62=require('base62');
var maxv= Base62.decode("ZZZZZZZZZZ");
var mmaxv = Base62.encode(maxv);
console.log("maxv=" +maxv+" mmaxv="+mmaxv);


>   maxv=839299365868340200 mmaxv=10000000000

Upgrade mocha to version 3.3.0

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/3.3.0

Is it possible to disable install-stats.js?

base62.js is one of dependency in my project. :)

I have one problem with install-stats.js in base62/scripts.
Internal network case, because install-stats.js tries to connect google analytics, so npm install takes too long time, and fails to connect in the end.
This makes build time to be increased.

Could you add timeout for this process or give any option to disable it?

Upgrade mocha to version 3.5.1

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/3.5.1

Upgrade supports-color to version 4.3.0

Libraries.io has found that there is a newer version of supports-color that this project depends on.

More info: https://libraries.io/npm/supports-color/4.3.0

The repository doesn't mention a license

I would like to use base62 in my project, but you haven't included a license, so I can't. Could you pick one? (MIT or similar would be great.)

Thanks in advance!

Should state clearly it's just for numbers

Base16 to Base64

What would be the proper way to convert base16 strings into base64 strings, and vice versa ?

For example: (b16) 0xF216E209761BB32986723 -> (b64) ????

Update NPM

I just used NPM to download the latest version, 0.1.1 and it doesn't give me the latest version from github.

Upgrade mocha to version 4.0.1

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/4.0.1

Install problem

Your recent change to the package json, specifically the postinstall where you're trying to scrape stats is causing install failures

"postinstall": "TID=UA-265870-43 node scripts/install-stats.js"

Upgrade growl to version 1.10.3

Libraries.io has found that there is a newer version of growl that this project depends on.

More info: https://libraries.io/npm/growl/1.10.3

Upgrade commander to version 2.11.0

Libraries.io has found that there is a newer version of commander that this project depends on.

More info: https://libraries.io/npm/commander/2.11.0

Where is the tag for 1.2.8?

Hi, I see that a version 1.2.8 is listed on npm but I cannot find the tag here. Could you push it by chance? Thanks.

Upgrade mocha to version 2.5.0

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/2.5.0

Upgrade growl to version 1.10.4

Libraries.io has found that there is a newer version of growl that this project depends on.

More info: https://libraries.io/npm/growl/1.10.4

Upgrade mocha to version 3.1.0

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/3.1.0

Upgrade growl to version 1.10.1

Libraries.io has found that there is a newer version of growl that this project depends on.

More info: https://libraries.io/npm/growl/1.10.1

Upgrade mocha to version 3.2.0

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/3.2.0

Upgrade brace-expansion to version 1.1.11

Libraries.io has found that there is a newer version of brace-expansion that this project depends on.

More info: https://libraries.io/npm/brace-expansion/1.1.11

modular ES6 variant

As discussed elsewhere, I found myself accidentally re-implementing Base62.js in modular ES6: https://github.com/FND/base62
Now that I've recognized my folly, rather than imposing yet another npm package on the world, it seems worth first considering to merge our efforts instead.

My goal there was to create an efficient library that works in any JavaScript engine (i.e. browsers as well as Node, Nashorn etc.). The only expectation is either ES2015 support or DIY ES5 transpiling - which doesn't have to be painful these days.

ES6 helps not just with readability and hipster cred, but modular exports also avoid including unused bits (think tree shaking).

Preliminary benchmarking (I'm not much of an authority there) suggests that my version is at least on par with the current implementation.

I realize that in its current form, my version's API and aforementioned expectations aren't compatible with Base62.js v1.x, but that's not necessarily a bad thing and still up for debate.

Let me know what you think. (I've tried writing concise and readable code as well as useful commit messages.)

Upgrade debug to version 1.0.5

Libraries.io has found that there is a newer version of debug that this project depends on.

More info: https://libraries.io/npm/debug/1.0.5

Upgrade supports-color to version 4.2.0

Libraries.io has found that there is a newer version of supports-color that this project depends on.

More info: https://libraries.io/npm/supports-color/4.2.0

ISSUE: If the input string starts with 0 then that 0 is lost during encoding.

If the input string starts with 0 then that 0 is lost during encoding.
for e.g. if the input is 0zebra then b62.encode(b62.decode("0zebra")) outputs zebra
b62.encode(b62.decode("0000zebra")) //zebra

Upgrade brace-expansion to version 1.1.10

Libraries.io has found that there is a newer version of brace-expansion that this project depends on.

More info: https://libraries.io/npm/brace-expansion/1.1.10

Upgrade mocha to version 4.0.0

Libraries.io has found that there is a newer version of mocha that this project depends on.

More info: https://libraries.io/npm/mocha/4.0.0

Upgrade supports-color to version 4.4.0

Libraries.io has found that there is a newer version of supports-color that this project depends on.

More info: https://libraries.io/npm/supports-color/4.4.0

Upgrade supports-color to version 4.0.0

Libraries.io has found that there is a newer version of supports-color that this project depends on.

More info: https://libraries.io/npm/supports-color/4.0.0

Your default character set does not match your examples, and all other converters out there

FYI, this tripped me up for a bit. You use G7 converting to 999 in your example. But with your default character set, decode('G7') == 2611.

You need to run:
b.setCharacterSet('0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz');
to get decode('G7') == 999

Upgrade debug to version 3.1.0

Libraries.io has found that there is a newer version of debug that this project depends on.

More info: https://libraries.io/npm/debug/3.1.0

Upgrade commander to version 2.10.0

Libraries.io has found that there is a newer version of commander that this project depends on.

More info: https://libraries.io/npm/commander/2.10.0

Upgrade debug to version 2.6.9

Libraries.io has found that there is a newer version of debug that this project depends on.

More info: https://libraries.io/npm/debug/2.6.9

`TID` is not recognized command.

@andrew I just now saw that you have released a patch to fix this error by adding a fallback. This error was happening to me in windows, but passed in linux. Why not use cross-env? This package will enable to use same command line environment variables.

Thank you for immediately fixing the issue!

base62 / base62.js Goto Github PK

base62.js's People

Contributors

Stargazers

Watchers

Forkers

base62.js's Issues

Recommend Projects

Recommend Topics

Recommend Org