Closed raphael10-collab closed 3 years ago
Your webpack configuration is broken. A cursory web search led me to this: https://github.com/Level/leveldown/issues/725#issuecomment-755205501 - it makes the No native build
error go away for me.
@achingbrain
Thank you. Unfortunately this solves partially but not completely.
Once set in webpack.main.js:
node: {
global: true,
__dirname: true,
__filename: true
}
if in package.json the main path is set to:
"main": "./.webpack/main"
I get no error but the ipfs peers disappear :
If I set main path to "main": "src/main.ts"
then the ipfs working comes back
But, according to the Electron-Forge documentation the main path has to be set to ./.webpack/main
: https://www.electronforge.io/config/plugins/webpack#project-setup
I'm getting this error once I change the location of main in package.json to :
"main": ".webpack/main"
, as suggested by the documentation: https://www.electronforge.io/config/plugins/webpack#project-setupThis is the package.json :
In order to better spot and solve the problem, I've put the code here: https://github.com/raphael10-collab/ForgeElectron Just git clone -> yarn -> yarn install
I do not know if it's a problem which has to be solved by "Electron-Forge people" or by "Ipfs people". But it's a fact that this problem arises when using Ipfs with Electron-Forge
I opened an issue also in the GitHub's Electron-Forge page: https://github.com/electron-userland/electron-forge/issues/2146