conf VS electron-store

Wow. There is even one package to not use a JavaScript object: https://www.npmjs.com/package/conf

info on XDG: [the XDG spec](https://standards.freedesktop.org/basedir-spec/basedir-spec-...)

tools that respect XDG, for fellow JS CLI developers:

- https://github.com/davidtheclark/cosmiconfig Find and load configuration from a package.json property, rc file, or CommonJS module. [Check `searchPaths` to implement XDG spec compliance.](https://github.com/davidtheclark/cosmiconfig/issues/152)

- Sindre's libraries use [`env-paths`](https://github.com/sindresorhus/env-paths#pathsconfig) to get paths compliant with this.

- https://github.com/sindresorhus/conf simple config storing (maybe try [conf-cli](https://github.com/natzcam/conf-cli) to manipulate if needed) the successor to [configstore](https://github.com/sindresorhus/conf#how-is-this-different-f...)

- https://github.com/jonschlinkert/data-store conf like datastore but in the shclinkerverse

Now, we implement history feature through which we can view the lastly created password through the -h or --history flag. For this purpose we use conf package. But first, let's create the flag feature. We use process.argvfor this purpose, process.argv is an inbuilt API used to get the arguments passed via command line like -h. We will slice it to remove the first two indexes of it to get relevant data only.

conf:This package allows us to save persistent information on the user’s machine. We will be using it to save the user’s todo list

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