It would be nice to have a way to debug app built with package or build-installer

[calebl]

I've run into a few things that work with npm run desktop that don't work once I packaged the app. Currently, there doesn't seem to be a way to enable debugging on production apps.

[wojtkowiak]

Hey @calebl I would be super interested in getting to know in detail what were the problems you have mentioned. This kind of problems are very critical to this integration.

Currently, there doesn't seem to be a way to enable debugging on production apps.

What would help you in particular? Do you have any ideas? So far I have planned to add an option to redirect the logs from the chrome console to a file (that would also log in production apps).

I am also thinking about the possibility of allowing to include dev tools in a production build.

[tzapu]

we could of used something similar as well, when debugging why some windows didn t appear on other OS s. in the end we ran the production executable from cmd and got the errors there

[calebl]

I think having the option to include dev tools in a production build would be the most useful to me. Currently, I've cloned a local copy of the repo to make this possible. It would be great to have a --debug flag for use with package and build-installer.

I haven't tracked down all of the issues I've had yet, but I am seeing some crashes caused by a module I wrote to download remote assets and store them locally for offline. The app runs without issue using npm run desktop, but crashes on the first startup when used with package or build-installer (it works when restarted). Not sure what the difference is yet.