The approach I use is documented in the readme. I develop from electron, rather than standalone server + browser (though the latter is still supported for work not requiring IPC.) It's working well enough that I haven't rushed to implement webpack/livereload.
mainis still copied, not webpacked.- Webpack + HMR is still on my TODO list. (It's possible, but I haven't finished. Though should be easier without a separate worker process now...)
- ...So changes to main require restarting manually.
- On the plus side, 'build' is effectively just a
cp -R, and startup is reasonably fast
- On the plus side, 'build' is effectively just a
- I haven't felt the need yet, but you can install react & redux devtools extensions in electron if desired. That's the only thing missing vs. browser dev, IMHO.
- steve is right in that electron is the biggest risk; it's covered well in the docs
- this paper covers a lot of the same material but might be worth a skim
- WIP security doc
- WIP server doc discusses TLS & pairing
- (probably not relevant to architect?) recharts doesn't really work inside a grid layout, I'm hoping they fix it before I get there.
- I found working with native menus a lot easier than trying to build everything into the UI (a la NC) — keyboard shortcuts work automatically, for example
- native D&D 'just works'; architect may be able to use it?
- IPC is used in a few cases to coordinate native & web. If it gets any more involved, I'd consider reintroducing sockets to replace that part of it (but still haven't seen a use case for device API)