Distributed code component manager

It helps you make code components such as functions, classes and more reusable with zero initial configuration. Creating a Bit component and using it across repositories prevents the need to duplicate or re-invent it over and over again.

Bit uses a distributed scoping system to organize your components and take care of their entire lifecycle. Scopes take care of versioning, dependency management, building and testing components in an isolated environment and more. You can create a scope anywhere or connect scopes together to create a distributed network.

• Use components across repositories. Use your functions/classes in multiple repos.

• Zero initial configuration. Transpiling and testing with simple commands.

• Scoping system. Orgenize your components in multiple scopes.

• Distributed. Create a scope anywhere you want with bit init --bare

• Component CI. Build and test execution in an isolated invironment.

• Fast dependency resolution. Performed on export.

• Quick modification. Update components with a single bit modify command.

• Simple versioning management. Simplified incremental versioning for easier update and maintenance.

• Semantic search engine. Find and use components created by you or your team.

npm install bit-bin -g

For more installation methods, please check our wiki's installation section.

Here is a getting started guide.

Head over to the Docs for more information.

Before Bit, we often found ourselves re-writing or duplicating code across repositories over and over again. This wasted time and effort while making our code base harder to maintain.

The only alternative was to spend time on boilerplating and build configuration. We also ended up having to maintain a git repo, package and CI for every small component. This required too much overhead to be practical.

We needed a tool that can save us the overhead of making code components reusable. We also needed to take care of our components through their entire lifecycle. We also wanted to collaborate by using and maintaining each other's components.

This compelled us to build Bit. It helped us get rid of hundreds of duplications, saved time an effort and made our code base much easier to maintain. It also proved valuable to performence and helped us get rid of tools we no longer needed. Bit made it practical to collaborate as a team working with the same components. In the long run, we hope Bit will help create dynamic sets of building blocks that will allow everyone to create anything.

Feedbacks are more than welcome: [email protected]

Contributions are always welcome, no matter how large or small. Before contributing, please read the code of conduct.

See Contributing.

Apache License, Version 2.0