JinjuType-safe CLIs for Node

Define flags, args and commands separately, compose them, and get fully typed input. Help, errors and exit codes are handled for you.

Get started
API reference
GitHub
ts
const 
deploy
 = 
command
({
	
description
: 'Deploy a site',
	
args
: [
arg
.
string
({ 
name
: 'site', 
description
: 'Site' }).
required
()],
	
flags
: {
		
env
: 
flag
.
string
({ 
description
: 'Env', 
choices
: ['dev', 'prod'] }),
		
force
: 
flag
.
boolean
({ 
alias
: 'f', 
description
: 'Skip checks' }),
	},
	
run
: ({ 
args
: [
site
], 
flags
: { 
env
, 
force
 } }) => {
	                              
env: "dev" | "prod" | undefined
	},
});

const 
app
 = 
jinju
({ 
commands
: { ':site': { 
deploy
 } } });

await 
app
.
run
();

// $ app my-site deploy --env prod -f

  • Typed from your definitions

    Flags and args resolve to exact types, such as 'fast' | 'safe' or URL[] | undefined. There are no interfaces to keep in sync.

  • Composable and immutable

    Define a flag once, then derive .required(), .multiple() and .default() variants. Scopes share flags and args across commands.

  • Command trees

    Nested subcommands, aliases, variadic args and dynamic segments like app my-site deploy, with mistakes caught at compile time.

  • Validation built in

    Numbers, URLs, emails, paths, choices, environment variables, custom parsers and any Standard Schema (zod, valibot, arktype).

  • Help and errors

    Generated --help pages, and every input error reported at once. Customise both by extending a template class.

  • Small and testable

    No runtime dependencies. Inject argv, env, stdout, stderr and the exit code to test in-process.