You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use the boilerplate with the node module "ursa" (version 0.9.4) which is a native module that needs compilation for my plateform.
For the record, I'm using node 8.11.4 and npm 5.6.0.
So in a vanilla electron-react-boilerplate project, I've included ursa in the ./app/package.json and installed it with npm i in the app/ folder or just run yarn in root folder for it to compile the native module. The compilation works like a charm, no issue here.
Problem is that when I import ursa from 'ursa' in the ./app/index.js and launch the project with yarn dev in root folder, I get the following error in the console, and the electron process crashes
As I read it somewhere, BIO_new_mem_buf seems to be a function from libssl > v0.9 and I have all the requirements installed on my machine (I've tried it with libssl-dev which is v1.1.0f-3+deb9u2 and libssl1.0-dev, doesn't change anything).
On github I've found many related issues to using a native module that fails to link to openssl functions on the local plateform like this fellow here but none of the proposed solutions seem to work for me.
I get the feeling this is related to my plateform and how the links to the ssl libraries are failing when running with the electron process in the boilerplate.
For info, I've also tried running the ursa module in a vanilla electron project (without the boilerplate and webpack) and it works fine...
Any help or just testing on your own plateform would be really appreciated in order to see if this is the default faulty behavior we get using the boilerplate (and help us locate what's going wrong and where)!
Thanks a lot
PS: same issue if I run the project in node 10.10.0 and npm 6.4.1
PPS: I'm using debian 9, a colleague's got the same issue running macOS 10, and another one using also debian 9
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi everyone,
I'm trying to use the boilerplate with the node module "ursa" (version 0.9.4) which is a native module that needs compilation for my plateform.
For the record, I'm using node 8.11.4 and npm 5.6.0.
So in a vanilla electron-react-boilerplate project, I've included ursa in the
./app/package.json
and installed it withnpm i
in theapp/
folder or just runyarn
in root folder for it to compile the native module. The compilation works like a charm, no issue here.Problem is that when I
import ursa from 'ursa'
in the./app/index.js
and launch the project withyarn dev
in root folder, I get the following error in the console, and the electron process crashesAs I read it somewhere,
BIO_new_mem_buf
seems to be a function from libssl > v0.9 and I have all the requirements installed on my machine (I've tried it withlibssl-dev
which is v1.1.0f-3+deb9u2 andlibssl1.0-dev
, doesn't change anything).On github I've found many related issues to using a native module that fails to link to openssl functions on the local plateform like this fellow here but none of the proposed solutions seem to work for me.
I get the feeling this is related to my plateform and how the links to the ssl libraries are failing when running with the electron process in the boilerplate.
For info, I've also tried running the ursa module in a vanilla electron project (without the boilerplate and webpack) and it works fine...
Any help or just testing on your own plateform would be really appreciated in order to see if this is the default faulty behavior we get using the boilerplate (and help us locate what's going wrong and where)!
Thanks a lot
PS: same issue if I run the project in node 10.10.0 and npm 6.4.1
PPS: I'm using debian 9, a colleague's got the same issue running macOS 10, and another one using also debian 9
The text was updated successfully, but these errors were encountered: