conf VS Bit

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

As part of my job, recently I'm working on integrating Vite (also Vitest) into a dev tool called Bit, which originally uses webpack in most of the cases. Basically, Bit is a component-driven development tool for various frontend frameworks and Node.js. In Bit, everything is a component and eventually consumed as an npm package. So technically, you would deal with all kinds of components as packages in your node_modules folder, whatever they are in CJS or ESM, need to be further transformed or not.

Using Bit and Bit Platform, components are shared and synced across separate repositories, allowing you to treat your poly-repo setup as one single virtual monorepo.

Before Bit became part of our workflow, sharing and collaborating on individual components felt like climbing a steep mountain. Managing dependencies, packaging, documentation, and setting up elaborate build tools wasn’t just time-consuming — it was frustrating. These setups often relied on third-party tools that were prone to issues, introducing bugs and bottlenecks along the way.

Bit Documentation

By leveraging tools like Bit and [Ripple CI], developers can unlock the full potential of build-time micro frontends, creating applications that are not only modular and maintainable but also efficient and cohesive. It’s time to give build-time integration the spotlight it deserves and embrace a future where distributed frontends are both powerful and user-friendly.

Bit. Composable software.

Some component collections like shadcn/ui offer a CLI tool to help you with the “copy-paste” process. Other tools like Bit can help you do the same with any UI library hosted on the Bit Platform. Any component can either be installed or copied into your project.

Bit has introduced a new entity to the world of web development: The Bit Component. In short, a Bit component can be thought of as a super-package. You can share it, install it, copy it, and even collaborate on it independently of any particular project setup.

Official Website