electron-builder | 易学教程

how to bundle git with an electron app

阅读更多关于 how to bundle git with an electron app

问题 I am developing an electron application for a client and they need an easy way to update the app as I work on it. I have found that the easiest way is to just include support for pulling from a git repo and this works fine in my tests and on the clients' machine. Recently, they tried to install the app on a new mac that does not have git installed. The client, who is not tech savvy, is having a lot of trouble installing git and it took me a while to walk them through downloading the installer

How can I get information about the file that launched my app?

阅读更多关于 How can I get information about the file that launched my app?

问题 Similar to How to get the arguments for opening file with electron app but the solution there is not working for me. Using: OS - Windows 10 Electron - https://github.com/castlabs/electron-releases.git#v1.8.7-vmp1010 electron-builde - v20.28.3 I have a an electron app build with electron-builder, and using the latter I have specified a custom file association, .custom . So when you double-click on a file with this extension, file.custom , the installed app opens. This file would have some data

Embed Mongodb with Electron

阅读更多关于 Embed Mongodb with Electron

问题 I am keeping MongoDB source code inside electron source code and running MongoDB using this command : const app = require('electron').app; const child_process = require('child_process'); const dbInstanceDir = app.getAppPath(); const startMongo = dbInstanceDir + mongodb/bin/mongod --dbpath mydbpath --port 27017 --logpath mylogfile child_process.exec(startMongo, (error, stdout, stderr) => { }); Above command is working while development but it not working after bundling. I am using electron

Electron dying without any information, what now?

阅读更多关于 Electron dying without any information, what now?

The app I'm building, when I compile it for distribution packing it with electron-builder, every now and then, dies, showing a blank screen and a disconnected devtools: Any ideas what's going on or how to start figuring out what's happening here? Listen for the uncaughtException event and log any error that you get. This will give you insight into what is happening. Then perform any cleanup if necessary and relaunch the app if desired. This allows your app to "recover" from crashes if it is intended to be long-running. //handle crashes and kill events process.on('uncaughtException', function

Managing application settings in an Electron application

阅读更多关于 Managing application settings in an Electron application

I'm curious to know how can one manage application settings in an Electron application ? I have found some excellent resources here ( Where to store user settings in Electron (Atom Shell) Application? , for example) and elsewhere when it comes to managing user settings but couldn't find anything related to managing application settings. To me, the difference between the two is that application settings could vary from environment to environment (dev/test/production) but would remain the same for all users of the application. They would contain things like API endpoints etc. User settings on

Embed Mongodb with Electron

阅读更多关于 Embed Mongodb with Electron

I am keeping MongoDB source code inside electron source code and running MongoDB using this command : const app = require('electron').app; const child_process = require('child_process'); const dbInstanceDir = app.getAppPath(); const startMongo = dbInstanceDir + mongodb/bin/mongod --dbpath mydbpath --port 27017 --logpath mylogfile child_process.exec(startMongo, (error, stdout, stderr) => { }); Above command is working while development but it not working after bundling. I am using electron builder to make bundle. MongoDB source code is at root level. As far as I know, you cannot package MongoDB

Where can I find the logs for my Electron app in production?

阅读更多关于 Where can I find the logs for my Electron app in production?

问题 I've built an app with Electron and used Electron-Builder to create a Squirrel windows installer and updater. It all works great but I'm having trouble debugging the production version of my app. Are the logs created by a console.log written somewhere on disk when using the production version? If so, where can I find them? Or are those all removed when compiling the executable? There must be some kind of log file for my app right? I've found the SquirrelSetupLog in C:\Users\Tieme\AppData

Signing installer for windows app using electron builder

阅读更多关于 Signing installer for windows app using electron builder

问题 I am using electron-builder for creating installer for my desktop app in windows by command build -w it cerates folder win-unpacked(for build) and win(for installer) here is my package.json { "name": "CoDesktopElectron", "version": "1.0.0", "description": "CoDesktopElectron", "homepage": "https://app.onepgr.com/", "author": "ankur", "private": true, scripts": { "postinstall": "install-app-deps", "start": "npm install && npm run compile && electron ./app", "compile": "rimraf app/out && tsc",

How to launch my electron app from a website

阅读更多关于 How to launch my electron app from a website

问题 We have an electron crypto app that signs transactions (among other things). We want other websites to have the ability to have a button that opens that electron app, pre-filled with some params (the transaction information). flow is: user clicks "make transaction" on some-crypto-site.com electron app opens up with pre-filled params user clicks "sign transaction" in electron app electron app does stuff behind the scenes electron app closes and sends a message to some-crypto-site.com This

Where can I find the logs for my Electron app in production?

阅读更多关于 Where can I find the logs for my Electron app in production?

I've built an app with Electron and used Electron-Builder to create a Squirrel windows installer and updater. It all works great but I'm having trouble debugging the production version of my app. Are the logs created by a console.log written somewhere on disk when using the production version? If so, where can I find them? Or are those all removed when compiling the executable? There must be some kind of log file for my app right? I've found the SquirrelSetupLog in C:\Users\Tieme\AppData\Local\MyApp\SquirrelSetupLog but that's not enough for debugging my production-only problem. Just came