Bare DocsReference
Authoritative descriptions of the Bare runtime, its CLI, building blocks, and the bare-* module catalog. Use this when you need a fact, not a tutorial.
Reference is the technical description of how Bare works. It's information-oriented: comprehensive, accurate, and dry. Use it to look up an API signature or a module.
If you're trying to accomplish a specific task, see How To. For the design rationale, see About Bare.
Pear is the platform on top. Install the pear CLI when you want peer-to-peer app distribution, over-the-air updates, and one command to stage and release—the core you write here moves across unchanged. Start on the Pear tab, or read How the stack fits together.
P2P is the peer-to-peer building blocks. Hypercore, Hyperswarm, Autobase, Hyperbee, Hyperdrive, HyperDHT, and Corestore—independent JavaScript modules for storage, discovery, and replication, with their own docs on the P2P tab. How the stack fits together maps the layers.
In this section
Bare
- Bare runtime API—the
Bareglobal: process properties, lifecycle, addons, threads, IPC. - Bare CLI—run a script or REPL with the
barecommand. - Bare Kit—the Worklet and IPC API for iOS, Android, and React Native.
- Native-addon CI prebuilds—building and publishing prebuilt native addons.
Module catalog
- Bare modules—the full
bare-*standard library, with the Node.js compatibility table.
For the peer-to-peer building blocks, helpers, and tools that run on top of Bare—Hypercore, Hyperswarm, Autobase, and the rest—see P2P's Reference. For Pear's CLI, configuration, and release tooling, see Pear's Reference.
Stability legend
Module pages call out a stability indicator. The four levels:
| Stability | Description |
|---|---|
| stable | Unlikely to change or be removed in the foreseeable future. |
| experimental | New, untested, or has known issues. |
| deprecated | Being removed or replaced in the future. |
| unstable | May change or be removed without warning. |