bit-bin

Bit

A virtual and distributed code component repository with a dynamic API.

Bit allows you to create and model components on a virtual Scope creating a dynamic API that contains nothing but the components actually used in your application. Bit components can be reused in different contexts (repositories, micro-services etc.) without the overhead of configuring and maintaining multiple repos, packages and tools or having to pull redundant code.

The case for Bit

Code components are the fundamental building blocks of any application. Different functionalities can and should be reused across different contexts, repositories and projects. In practice, this rarely happens. People often end up duplicating code everywhere or using vast libraries with static APIs that contain a lot of redundant code and dependencies they don’t really need. This happens for a few reasons:

• Initial overhead: To create a new repository and package for every small component you would have to create a VCS repository, create the package boilerplate (build, testing, etc.) and somehow make this process practical for a large set of components.

• Maintenance: Modifying a repository and a package takes time and forces you to go through multiple steps such as cloning, linking, debugging, committing, republishing and so on. Centralized registries also makes it hard to address the different levels of abstraction needed for multiple micro-packages. Build and install times quickly increase and dependency hell always feels near.

• Discoverability: It’s hard if not impossible to organize and search multiple repositories and packages to quickly find the components you need. People often used different terms to describe the same functionality, and there is no single source of truth to search and trust.

Bit relies on a different paradigm that never creates these problems in the first place. It allows you to use a new entity called a Bit Scope to create and model your components in a virtual repository with a dynamic API that allows your application to pull only the code it actually needs to run.

Creating a Bit component requires little to no initial configuration thanks to the nature of the component itself and Bit’s component environment that uses other components for compiling and testing your components. The Bit scope also manages your component end-to-end and prevents the need to use package managers built to handle large and complex packages and additional tools for transpiling and testing your components.

Bit is a single tool that allows you to create, find and reuse your components anywhere. It also works well for collaborating as a team.

Main features of Bit

• Virtual Scope. A Scope is a distributed dynamic codebase responsible for end-to-end management of code components. Scopes are where components are stored, tested, built and integrate with each other.

• Dynamic API. Define the components you need in your application to form a dynamic API made of these components alone, without pulling any redundant code or irrelevant dependencies.

• Component environment. Transpiling and testing are done by simply using other Bit components (compiler and tester), which you can reuse while creating any component with any superset or a testing framework in any context.

• Fast and predictable dependency resolution. Dependency resolution is performed on component export, so Bit doesn't have to perform any runtime resolution. This makes the use of components predictable, fast and always available.

• Discoverability. Bit has an integrated search engine that uses expressive linguistic models to make your components discoverable even when you forget the exact name you gave each component.

Installation

For our different installation methods, please visit our docs installation section.

Quick start

Here is a getting started guide.

Documentation

Docs

Bit Scope

Bit component

Bit on the server

CLI refrence

Feedback

Feedbacks are more than welcome: [e-mail]

Contributing

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

See Contributing.

License

Apache License, Version 2.0

Changelog

[0.3.3]

Fixed

• add posix as an optional dependency (windows)

Added

• specsResults verbose output after ci-update
• add bit clear-cache cmd
• now running clear cache before bit update