@plurnk/plurnk-execs-common
v1.8.0
Published
Universal subprocess executor for plurnk-service's exec scheme — one package exposing the shell + node + python floor plus whichever host interpreters (perl, ruby, php, lua, awk, bc, …) are present.
Maintainers
possumtechcomReadme
@plurnk/plurnk-execs-common
The universal subprocess executor for
plurnk-service's exec scheme. One
package covers the shell, Node, Python, and whichever supported host
interpreters are present. Node is guaranteed; the rest are detected.
A @plurnk/plurnk-execs-* sibling built on the plurnk-execs framework. Supersedes the former -sh, -node, -python packages (folded in here).
How it works
The manifest claims the subprocess tags. Per-tag probe() reports Node
unconditionally because the daemon already runs on it. A cheap command -v
detects every other interpreter, so one executor adapts to the host.
| Tag | Binary | Inline body via |
| -------------------------------- | ----------------- | ---------------------------------------- |
| sh 🐚 / bash 🐚 | sh / bash | -c <body> |
| node ⬢ | node | -e <body> (always available) |
| python / python3 🐍 | python3 | -c <body> |
| perl 🐪 / ruby 💎 / lua 🌙 | perl / ruby / lua | -e <body> |
| php 🐘 | php | -r <body> |
| deno 🦕 | deno | eval <body> |
| bun 🥟 | bun | -e <body> |
| tcl 🪶 | tclsh | stdin |
| bc 🧮 | bc | stdin (for example, 6 * 7) |
| awk 🪄 | awk | program arg, empty stdin (BEGIN { … }) |
A script or working directory — the (target) slot
The table above is the inline form: the body is the program. A file in the
(target) slot is instead the script each interpreter reads directly, and the
body becomes that script's stdin. A directory target becomes the working
directory and the body remains the inline program
({§executor-subprocess-routing}).
## EXEC0 [sh] (./deploy.sh)
yes
yes
no
## EXEC0 [python] (transform.py)
3
1
4
1
5The first operation answers a shell script's prompts through stdin. The second feeds records to a Python script.
All declared tags run host code, so every invocation is proposal-gated. The
current installed in-process evaluators are jq, SQLite, and WebAssembly; their
pure or read invocations bypass the proposal gate but still return through
the same next-turn stream path ({§executor-effect}). Input-processing
transforms (sed, input-driven awk) await an EXEC input-channel contract and
are not claimed here.
Configuration
Per-tag kill-switches (PLURNK_EXECS_<TAG>=0) and the
PLURNK_EXECS_ONLY allowlist are honored by framework discovery, uniformly
across every plugin ({§executor-policy}). A disabled tag is not registered and
never reaches this executor.
Tests
test:lint, test:unit. Live-eval tests auto-skip where the interpreter is absent.