1.2.2:
1.2.1 (do not use):
1.2.0 (do not use):
devDependencies
.mjs
package.json
updates.gitattributes
marks package-lock.json
as binarydist/hashids.min.map
to dist/hashids.min.js.map
1.1.4:
_encode
would crash because it can't handle those https://github.com/ivanakimov/hashids.js/issues/34
NOTE: do not use 1.1.3
, it wasn't re-built1.1.2:
package-lock.json
1.1.1:
hashids.js
to lib/hashids.js
README.md
cleanup1.1.0:
README.md
README.md
completely updatedexamples/
folder removed; all examples are now in the READMEImprovement: relaxed parameter checks to encode()
. All of these are allowed:
var hashids = new Hashids();
hashids.encode(1, 2, 3); // o2fXhV
hashids.encode([1, 2, 3]); // o2fXhV
hashids.encode('1', '2', '3'); // o2fXhV
hashids.encode(['1', '2', '3']); // o2fXhV
1.0.2:
charAt
) by @tauanz: https://github.com/ivanakimov/hashids.js/pull/151.0.1:
1.0.0:
Several public functions are renamed to be more appropriate:
encrypt()
changed to encode()
decrypt()
changed to decode()
encryptHex()
changed to encodeHex()
decryptHex()
changed to decodeHex()
Hashids was designed to encode integers, primary ids at most. We've had several requests to encrypt sensitive data with Hashids and this is the wrong algorithm for that. So to encourage more appropriate use, encrypt/decrypt
is being "downgraded" to encode/decode
.
Version tag added: 1.0
README.md
updated
0.3.0:
PRODUCED HASHES IN THIS VERSION ARE DIFFERENT THAN IN 0.1.4, DO NOT UPDATE IF YOU NEED THEM TO KEEP WORKING:
0.1.4:
0.1.3:
Warning: If you are using 0.1.2 or below, updating to this version will change your hashes.
0.1.2:
Warning: If you are using 0.1.1 or below, updating to this version will change your hashes.
encode/decode
to encrypt/decrypt
0.1.1:
0.1.0: