-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lodash broken, won't fix #32
Comments
@ekkis can you expand on how the bug manifests itself in SLP-SDK? What is the problem that it causes, exactly? |
the lodash owner has agreed to apply a patch, so this should be ok. will post more when done |
after a long and painful path, I couldn't figure out how to fix that pile of doodoo so I need to revert back to you guys. here's an example of how this breaks:
if you run the above (using the latest 3.3.0 version of SLP), you'll get something like:
which can be solved by applying the following patch:
please help? |
I tried recreating the bug. Thank you for the concise code example. This is the code I tried first and everything ran perfectly: // Used for debugging and iterrogating JS objects.
const util = require("util");
util.inspect.defaultOptions = {depth: 1};
const SLP = require('slp-sdk')
var slp = new SLP()
let val
// Creates a Buffer
val = slp.Mnemonic.toSeed('')
// Converts the Buffer to a string
val = val.toString('hex')
console.log(`val: ${util.inspect(val)}`)
// val: '4ed8d4b17698ddeaa1f1559f152f87b5d472f725ca86d341bd0276f1b61197e21dd5a391f9f5ed7340ff4d4513aab9cce44f9497a5e7ed85fd818876b6eb402e'
let ret = val.substr(0,16)
console.log(`ret: ${util.inspect(ret)}`)
// ret: '4ed8d4b17698ddea' It was only when I added this code at the top, that the bug you're reporting manifested itself: const jsp = require('js-prototype-lib');
jsp.install() I checked out the npm entry for js-prototype-lib and it says right at the top:
I've never used the The obvious solution to me, seems to be avoiding the use of this library. |
I ran |
I've submitted a patch to lodash that fixes this problem and it has been accepted: lodash/lodash#4290 I've also requested of the Babel team to upgrade to the fixed version of lodash: babel/babel#9966 when that team upgrades I'll need you guys to upgrade |
your module depends on lodash, which has a problem described here: https://github.com/lodash/lodash/issues/4247
as is evidenced by the thread, the lodash team is completely uncooperative, which means I can't use your module. the fix is small and simple. it is possible for your team to post-patch their module, fork it and fix it, or implement some other kind of solution?
The text was updated successfully, but these errors were encountered: