electron-settings VS electron-store

Use electron-settings (no updates in 2 years)

electron-settings https://github.com/nathanbuchar/electron-settings

One relatively straightforward way to do that would be to use something like electron-settings to record a little bit of persistent state data to disk. I.e., in your main.js as part of the app bootstrapping logic you would (1) attempt to read a "first_launch" flag from the settings, and (2) when missing, post the info to the server and write the first_launch=true flag to the settings so you know you've done it already on the next launch.

Not quite a database, but I use electron-store for persistent storage. It has a super simple API, and it stores data in a config.json file that’s mostly hidden from the user unless they know where to look.

The electron-store package works well with simple data.

I've seen electron-store, but it seems to be a volatile store. Each time I open the app, it seems I must create a new Store(). The doc explains clearly how to perform crud operation in a new store, but not how to retrieve existing data when re-opening the app 10 days later. If the lib can actually do it, how to do so?

With Electron, you have disk access via Node.js (fs.writeFile, etc), so you can save user preferences to the user's hard drive. See https://github.com/sindresorhus/electron-store for a library that makes it super easy and provides you with some nice conventions for working with the file system from an Electron app.

Use electron-store

https://github.com/sindresorhus/electron-store/issues/49 Links to internal test that shows how to pass types to electron-store

GitHub - sindresorhus/electron-store: Simple data persistence for your Electron app or module - Save and load user preferences, app state, cache, etc