New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not required in electron apps anymore? #174
Comments
I am just working on how to persist app data inside an electron app, and just came across both these packages and this issue. How is On
but as far as I can see, the API is exactly the same, including both of them having the |
Some benefits of using
|
@ivancuric Multiple Electron processes and multiple Node.js processes are not the same. Electron does have multiple processes, but only one process, the main process, can write to the store directly. For Node.js, however, multiple independent processes could write to the store. |
Would it be a good idea to expose I am already using a global state management library, with some stores holding persistent/serializable data. It seems like a good idea to perhaps use |
As of electron 12, this module may not be needed anymore. As far as my tests goes, just the basic conf module works just fine.
electron.remote
deprecation was fixed withipc
, but may be completely unnecessary.conf
now gets the correct parentDir values when used with electron directly, unlike earlier versions.I tested this with Electron on linux, using basic
npm start
, as anAppImage
, anddeb
andsnap
packages. They all work fine withconf
.I have not tested with electron 11, this may be true for that as well.
The text was updated successfully, but these errors were encountered: