In the example project, the electron and the React code are in separate files and only communicate using events. You could access the file system from the electron specific files, so you would never actually have to handle files in the React part of the application. What needs to be done will be sent by React and acted upon by electron
Other than that, you can eject from CRA environment and then modify the config according to your needs.
If your project relies heavily on the file system, then this might not be the React boilerplate you are looking for.
This boilerplate is aimed at beginners and has minimal number of packages required for developing and publishing
In the example project, the electron and the React code are in separate files and only communicate using events. You could access the file system from the electron specific files, so you would never actually have to handle files in the React part of the application. What needs to be done will be sent by React and acted upon by electron
Other than that, you can eject from CRA environment and then modify the config according to your needs.
If your project relies heavily on the file system, then this might not be the React boilerplate you are looking for.
This boilerplate is aimed at beginners and has minimal number of packages required for developing and publishing
Take a look at Electron React Boilerplate for a more rounded boilerplate