[Electron] TypeError: Cannot read property 'randomBytes' of undefined about bcrypto HOT 7 CLOSED

      at Object.randomBytes (node_modules/bcrypto/lib/native/random.js:20:18)
      at Function.randomBits (node_modules/bcrypto/lib/js/bn.js:3459:25)

This stack trace is confusing. Why does electron succeed at dynamically loading the binding? The random object is always on the exposed binding no matter what. Is electron does giving us an empty object for compatibility purposes?

but does not enter the catch block here

@supaiku0, what about NODE_BACKEND=node. Does that give any better results?

We only fall back to the JS random backend in the browser (which uses getRandomValues() instead of the crypto module).

I'm still fuzzy on what electron does/doesn't support and there doesn't seem to be a simple writeup anywhere. Personally I prefer not to touch electron, so I'm basically shooting in the dark here.

from bcrypto.

Possible duplicate issue: #15

Looks like the recommendation for now is to fall back to the JavaScript methods.

from bcrypto.

The environment variable is NODE_BACKEND=<js|node>

from bcrypto.

Thanks for the reply. I tried playing around with NODE_BACKEND=js before and the issue still persists:

    console.log node_modules/bcrypto/lib/native/binding.js:9
      js
    console.log node_modules/bcrypto/lib/native/binding.js:11
      boom
    console.log node_modules/bcrypto/lib/random.js:11
      all ok

In other words, it throws the exception here:
https://github.com/bcoin-org/bcrypto/blob/master/lib/native/binding.js#L9

but does not enter the catch block here:
https://github.com/bcoin-org/bcrypto/blob/master/lib/random.js#L12

from bcrypto.

Also, is there an easy way to detect electron? Do they expose a property on the process object or something?

from bcrypto.

It looks like process.versions.electron is set when running in electron.

electron/electron#2288 (comment)

from bcrypto.

@chjj @tynes This is a bit embarassing, but it's not actually Electron at fault here. I was only able to reproduce the error when running unit tests via jest and for some reason I mixed it up with Electron. I can no longer reproduce it after I wiped everything on my Linux system. It must have been a local issue on my side.

Sorry, for the confusion!

from bcrypto.