conf VS registry

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

More important than the namespace is who published the package. I'm more inclined to trust an individual I know who takes security than a namespace that may change hands.

NPM exposes that info in the _npmUser field: https://github.com/npm/registry/blob/master/docs/REGISTRY-AP.... That gives "name" (NPM username) and email.

While there are thousands of packages, I bet there's a much smaller number of publishers to worry about.

I can't find anything about it in their docs. https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md

https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md here are the docs. I was getting 122ms responses instead of 9000 on the old one.

My first instinct was to work with the public API of the npm registry. This sounds like a very good idea, but you will soon run into a set of problems (cache, private registry etc..).

There is no need to obtain an API key or token for querying NPM registry API. For the dashboard, I use only the endpoint that provides the data about a package downloads count - https://api.npmjs.org/downloads/. You can read more about it here.

While many people regularly use npm's website to discover packages, only a few know that npm also provides a public REST API accessible at registry.npmjs.org.

Or roll your own, docs here: https://github.com/npm/registry/blob/master/docs/download-counts.md