@arcships/rutis-bun

The Bun runtime of rutis: runs JavaScript and TypeScript plugins in Bun for a rutis host.

A host starts it as one process and runs plugins in it as rows named bun:<module>:

{
  "runtimes": { "bun": { "project": "." } },
  "rows": [
    { "id": "weather", "name": "bun:@acme/weather" },
    { "id": "report", "name": "bun:./report.ts", "inject": ["weather"] }
  ]
}

• Plugins are written with @arcships/rutis (definePlugin), or as a module exporting apply(ctx, config) with inject, optional (services used when there, read with ctx.get; rutis-host 0.20 or later), config and, optionally, provides (what ctx.provide provides reaches rutis without it).
• Events are one bus across every plugin, runtime and linked node (rutis 0.13): ctx.on(name, listener) registers with the host by itself and returns a disposer; ctx.emit / parallel / serial / waterfall / bail reach listeners in any language, with the same results as in one process; ctx.filter picks listeners. On unload the row's ctx.signal is aborted and its running listeners are waited for. See events.
• Modules resolve from the project: npm names and subpaths from its node_modules, ./paths relative to it. Install plugins with bun add.
• Nothing is installed or read behind the host's back: the runtime always runs with --no-install (a missing package fails, it is never downloaded) and --no-env-file (the environment is what the host gives). The project's bunfig.toml applies, as the project's own configuration.
• Synchronous calls are re-entrant: while a plugin's synchronous call into rutis waits, calls into this runtime still run, so runtimes that call each other never wait for each other for ever. A plugin's service may therefore be called while that plugin is inside a synchronous call: do not hold a lock across a call into rutis.
• An uncaught error ends the process, and with it every service of this runtime.
• Reloading a row imports its module again when the file changed; the modules it imports stay loaded (restart the runtime to replace those).
• Packages installed while the runtime runs are found after the runtime restarts: a Bun process remembers that a package was missing.

Bun 1.4 or later. Besides running on the host's machine (local channels), it runs as a remote runtime: listening (listen:ws://…, listen:wss://…) or dialing a rutis access point (dial:ws://…, dial:wss://…); see the Bun plugin guide.

Embedding hosts start it with rutis_host::connect::SpawnPlugin::new("bun", rutis_host::languages::bun::launcher(…), project) (Rust).