fiber_shell 1.0.0

Typed shell command builder for Dart and Flutter desktop: CLI tools wrapped as classes, with pipes, chaining and elevation run in Dart instead of through a shell.

Changelog

1.0.0

First release.

Core

• CommandBuilder<T>, the base every wrapper extends. One method is one option, and each option returns the concrete wrapper, so a chain stays typed to the end. Four helpers cover the argument shapes tools use: token, pair, joined and joinedAll.
• Four ways to run a command: execute() with stdio inherited, output() which captures both streams and never throws, writeTo(File) for stdout into a file, and background() for a job you keep a handle on.
• ShellResult, returned by output(): exitCode, success, failed, text, lines, error, bytes, duration, textOrNull and orThrow(). Output is kept undecoded, so the same type carries text and binary alike.
• ShellException, thrown by the runners that treat a non-zero status as fatal.
• Pipes through the | operator. Every stage starts at once and each stdout is wired into the next stdin through Dart streams. The status follows set -o pipefail: the rightmost stage that failed, or zero when they all succeeded.
• Chaining through and(), or() and then(), standing in for &&, || and ;. Dart cannot overload the first two, so they are named rather than guessed at.
• asRoot(), which marks the command rather than the run, so elevation survives being piped or chained. It adds sudo on Linux and leaves the command untouched elsewhere.
• line, which renders a command, a pipeline or a whole chain as a terminal would show it, without running it.
• BackgroundJob with pid, wait() and kill([signal]).
• Helpers for the tools that may not be installed: commandExists(name) and waitUntil(cmd, interval:, timeout:).
• Lower-level entry points for callers that already hold an argv: sh, capture, captureWithStdin, shToFile, captureResult, commandLine, commandArgv and privileged.

Every runner takes cwd and env; output() also takes input for stdin. Nothing is ever interpolated into a string, so there is nothing to escape.

Commands: cross-platform

Facade	Tool
Curl	curl
Deno	deno
Direnv	direnv
Docker	docker
DockerCompose	docker compose
Git	git
Jq	jq
Npm	npm
OpenSSL	openssl
PgDump	pg_dump
PgRestore	pg_restore
Psql	psql
Python3	python3
Scp	scp
Ssh	ssh
SshKeygen	ssh-keygen
Tar	tar

Commands: Unix

Present on macOS and Linux, and on Windows only through a POSIX layer.

Facade	Tool
Awk	awk
Bash	bash
Chmod	chmod
Chown	chown
Cp	cp
Du	du
Find	find
Grep	grep
Install	install
Kill	kill
Ln	ln
Lsof	lsof
Mkdir	mkdir
Ps	ps
Rm	rm
Sed	sed
Sh	sh
Tee	tee
Xargs	xargs

Commands: Linux

Facade	Tool
AptGet	apt-get
Ip	ip
Iptables	iptables
Journalctl	journalctl
SecretTool	secret-tool
Ss	ss
Sysctl	sysctl
Systemctl	systemctl
Ufw	ufw
Usermod	usermod
Wg	wg

Commands: macOS

Facade	Tool
Caffeinate	caffeinate
Defaults	defaults
Diskutil	diskutil
Dscl	dscl
Launchctl	launchctl
Networksetup	networksetup
Plutil	plutil
Pmset	pmset
Scutil	scutil
Security	security
Softwareupdate	softwareupdate

Commands: Windows

Facade	Tool
Cmd	cmd.exe
Icacls	icacls
Netsh	netsh
PowerShell	powershell
Reg	reg.exe
Robocopy	robocopy
Sc	sc.exe
Schtasks	schtasks
Taskkill	taskkill
Tasklist	tasklist

Every wrapper documents the tool it covers: which platforms have it, which of its options bite in automation, and the traps worth knowing about before reaching for a flag.

Docs and tests

• example/ holds a runnable tour in eight chapters, from a first command to writing your own wrapper.
• The test suite covers the builders, ShellResult, the runners, pipelines, chaining and background jobs, plus a structural pass that guards the barrel exports and the wrapper contract.