reactn VS electron-react-boilerplate

Have a look at ReactN

If you want to move to hooks for state management I suggest ReactN.

ReactN because it demonstrated engaging with and supporting customers to balance priorities and deliver results.

My open source React state management library ReactN helped me get a job at AWS, because it showed customer obsession.

I love ReactN.

Look into ReactN which uses hooks, has lower overhead, no boilerplate, and is much easier to use and learn than Redux.

I myself started a few years ago using ReactN which intends to implement global state management in a similar way like the local state in react works. But since this is a monolithic store too I recently switched to (the very unknown) React Capsule which is from the same dev, extremely lightweight, similar to recoil and intends to use encapsulated state which can be used either in plain JS, in class components, as well as in function components.

I am working on a project where I need to build a desktop app in Electron. The majority of functionality will be built in React, but there will be a part where we need to integrate a 3rd party static HTML magazine. I need some advice on how to do this. I am building a proof of concept app currently and I have based it on this https://github.com/chentsulin/electron-react-boilerplate

I am using electron-react-boilerplate to create an Electron-React app. The dev tools show up on the screen by default. How can I make the dev tools only appear when I ask for them and not show up on launch?

Using this boilerplate as reference I created an Electron app. It uses webpack to bundle the scripts and express server to host it.