Reference: Bare Runtime, CLI & Modules

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 of Bare. Everything here runs on Bare on its own. Install the pear CLI when you also want peer-to-peer app distribution, over-the-air updates, and one command to stage and release—the core you write for Bare moves across unchanged. Start on the Pear tab, or read How Pear and Bare fit together.

In this section

Bare

Bare runtime API—the Bare global: process properties, lifecycle, addons, threads, IPC.
Bare CLI—run a script or REPL with the bare command.
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.

Building blocks

The core peer-to-peer primitives Bare (and Pear) are built on:

Hypercore, Hyperbee, Hyperdrive, Autobase, HyperDHT, Hyperswarm.

Helpers

Higher-level utilities that combine the building blocks:

Corestore, Localdrive, Mirrordrive, Secretstream, Compact-encoding, Protomux.

Tools

CLI utilities built on Bare:

Hypershell, Hypertele, Hyperbeam, Hyperssh, Drives.

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.

Reference