Skip to main content

Dojo

@strip-mall-karate-company/dojov2026.10.26.1· MIT· 5d agoBEHAVIORSACCEPTED WARNINGS
01README

Show and build Dojo plans with doj-plan-build, and order a plans checkout into dependency waves for building.

02Behaviors1
@strip-mall-karate-company/dojov2026.10.26.1dojo.ts

Global Arguments

ArgumentTypeDescription
checkoutstringPath to a dojo-plans checkout: one directory per package, each with a plan.fnl
planBuild?stringThe doj-plan-build program, a path or a name on PATH
target?stringThe package target to show and build for, such as x86_64-linux
root?stringDOJ_ROOT_PATH for builds: where packages are installed and sources cached (default /doj)
keyPath?stringDOJ_CACHE_KEY_PATH: where origin signing keys are
outputPath?stringDOJ_OUTPUT_PATH: where built artifacts are copied
doj?stringDOJ_BIN: the doj program builds use to resolve installed packages and sign artifacts
baseOrder?stringThe base toolchain's build order, a file in the plans checkout: these plans build first, in this order
fn show(plan: string)
Read a plan's metadata for the target with doj-plan-build show
ArgumentTypeDescription
planstringThe plan's directory name in the checkout
fn build()
Build a plan with doj-plan-build, unless its package from the same plan content is installed or a plan it depends on failed its last build
fn order(plans?: array, withDependencies?: boolean)
Order plans into dependency waves for building, with their dependencies
ArgumentTypeDescription
plans?arrayPlans to build, by directory name; empty means every plan in the checkout
withDependencies?booleanAdd every plan the requested ones depend on, build or run, through scaffoldings

Resources

plan(infinite)— A plan's metadata for the target, from doj-plan-build show
build(infinite)— A plan's last build: the package's ident, prefix and artifact, or that it failed
order(infinite)— Plans in dependency order, as waves

Files

log(text/plain)— A build's output
03Stats
A
100 / 100
Downloads
1
Archive size
15.7 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License2/2earned
  • Verified public repository2/2earned

05Platforms