bit docs

bit is the package manager for H#, Hacker Lang and HackerScript. It is written 100% in H# and statically linked.

Quick start

bit init myapp --lang h#     # or hl, hs
cd myapp
bit                           # does everything Bit.hk describes

A bare bit reads Bit.hk, installs the missing dependencies, builds with [default-build] and, if you asked for it, runs the result.

Bit.hk

[package]
-> name        => myapp
-> version     => 0.1.0
-> lang        => h#            ;; h# | hl | hs   (several: h#, hs)

[build]
-> link   => static             ;; the only mode
-> target => h#                 ;; language toolchain (or a platform like linux-aarch64)

[lib]
-> output => hlib               ;; hlib | so | a | obj

[default-build]                 ;; what a bare `bit` does
-> profile => release
-> run     => true

[dependencies]
-> mold => *
-> tui  => rev v1.0
-> mine => path ../mine

[commands]                      ;; your own `bit deploy`
-> deploy => scp cache/build/release/myapp server:/opt/
--> description => Copy the release build to the server

Section	Purpose
`[package]`	name, version, description, authors, license, `lang`
`[layout]`	where the code is. Auto-detected: `src/` = H#, `cmd/` + `lib/` = HackerScript. Hacker Lang needs `hl-entry`.
`[build]`	`target` (h# / hl / hs), `platform`, `link` (static), `mem-mode`, `flags`
`[lib]`	library output: hlib (default), so, a, obj
`[default-build]`	`profile`, `target`, `platform`, `emit`, `run`, `args`, `before`, `after`
`[dependencies]`	`*`, `rev X`, `git URL [rev]`, `path DIR`
`[commands]`	custom commands, run as `bit <name>` (extra args are appended or fill `{args}`)
`[hooks]`	`pre-build`, `post-build`
`[workspace]`	`members` — the workspace root's `cache/` is shared

Where things live

`~/.hackeros/libs/<name>/<commit>/`	installed libraries (`current` → active commit)
`~/.hackeros/bit/bit.lock`	what is installed, with checksums
`<project>/cache/`	build outputs and links (no `build/` directory — same idea as virus)
`<project>/Bit.lock`	the commits + checksums your project resolved to — commit it

Statically linked, checksummed

Every library is built and linked statically; link => dynamic and extern dynamic are rejected. On install, bit hashes the library's files (sha256 over the sorted per-file hashes, independent of install location) and stores the result in bit.lock. bit verify re-checks it, and a Bit.lock pin that no longer matches fails the build instead of being trusted.

Commands

bit init [name] [--lang h#|hl|hs] [--lib]
bit build [--release] [--target h#|hl|hs] [--platform linux-aarch64] [--emit bin|hlib|so|a|obj]
bit run [-- args]        bit check        bit clean [--all]
bit install [name|git-url] [--output hlib|so|a|obj] [--no-build]
bit add <name> [rev]     bit remove <name>    bit upgrade [name]
bit search [text|all] [--lang hl]     bit info <name>     bit list
bit update       bit verify       bit doctor      bit langs
bit publish      bit commands     bit x <custom>

Publishing a library

There is no upload step. Run bit publish in your library — it validates Bit.hk and prints an index entry. Add it to index/repository.json and open a pull request; CI checks it before it lands.

{
  "name": "mylib",
  "target": "https://github.com/you/mylib",
  "description": "What it does.",
  "tags": ["tui"],
  "lang": "hsharp",
  "author": "You"
}