Open PeterBenko opened 9 months ago
This is the relevant code:
When starting in dev mode, Bruno tries to open http://localhost:3000
. When run in production mode, Bruno opens the JavaScript bundle included in the app.
If you try to run Bruno from source, make sure to run npm run dev:web
before starting electron.
Nice, straight to the point!
However, I would postulate that isDev
isn't the right tool for this use case and should actually be app.isPackaged.
In the recent times when developing an Electron app - and having ELECTRON_IS_DEV
permanently turned on - I leaned to expect many other apps opening the dev tools, which I understand - it basically flips them into debug mode. However, none of them straight up broke like Bruno did.
The decision to use the dev-server served content isn't something that should be based on the debug
flag. I'd say it should either be a run argument (like --useDevServer) or the above mentioned app.isPackaged
check. Is Bruno ever expected to run not packaged in production?
I'm open to creating a PR for either of the fixes :)
Yeah, you're right, app.isPackaged would totally be the better option here. You can create a PR for this, if you want, we would appreciate it.
@Its-treason Any update on this? We develop an Electron based app for which we set Electron_is_dev to 1. This means we can't use Bruno at the same time.
@Its-treason Any update on this? We develop an Electron based app for which we set Electron_is_dev to 1. This means we can't use Bruno at the same time.
Hey, I just added my Approved to the PR, but I cannot give you an ETA on when this will be merged. But it is a small change, so probably soon. CC @sanjai0py for visibility.
The main window is white when starting Bruno while the
ELECTRON_IS_DEV
env variable is set to1
. Importing / trying to import collections has no influence on the main window.Tested on:
MacOS @ v1.5.1
Windows 10 @ v1.4.0 & v1.5.0 & v1.5.1