Chris Veness

npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

Would it not be possible for SimpleMDE to remove any 'required' attribute from the text area and apply it to the markdown control? It's a while since I looked at...

@landart, yes, that's the sort of thing I had in mind. It could perhaps be generalised along the lines of (roughly) ``` const originalElement = document.querySelect('#original-text-area'); const mirrorElement = document.querySelect('.CodeMirror...

Since @popomore has apparently abandoned koa-proxy, could you see if npm would transfer the package name to you for you to take the project over? - https://docs.npmjs.com/misc/disputes I think it...

I think Barry may have abandoned this project. If you are using Node.js v10.5.0+, you could try my [scrypt-kdf](https://www.npmjs.com/package/scrypt-kdf), which is a simple pure-JS wrapper around the native OpenSSL implementation...

The dependency appears to be coming from [scrypt.js](https://www.npmjs.com/package/scrypt.js) (which no longer has a github repository), which is a dependency of [ethereumjs-wallet](https://www.npmjs.com/package/ethereumjs-wallet), in turn a dependency of [ganache-core](https://www.npmjs.com/package/ganache-core), in turn a...

I don't know about any substitute for [scrypt.js](https://www.npmjs.com/package/scrypt.js), but the collaborator listed on npm is @axic, who is also a collaborator on [ethereumjs-wallet](https://www.npmjs.com/package/ethereumjs-wallet), so it might be worth reaching out...

@axic – for Node.js prior to 10.5.0, and for browser, [scrypt-async](https://www.npmjs.com/package/scrypt-async) looks a good alternative to the OpenSSL implementation of scrypt. Edit: [scrypt-async](https://www.npmjs.com/package/scrypt-async) can be used as a polyfill for...

Having a quick look at [scrypt-async-js](/dchest/scrypt-async-js#options), I like @dchest’s idea of accepting either N or logN. You could do something like `if (params.N > 256) params.N = Math.log(params.N)*Math.LOG2E;`. I don’t...

Colin Percival says “The parameter N must be a power of 2 greater than 1” ([www.tarsnap.com/scrypt.html](http://www.tarsnap.com/scrypt.html)), so allowing any value of N would not seem a good idea for standardisation....