Skip to content
jess
guide

Getting Started

Install jess, write a script, make it a package, and set up an editor that knows the types.

Four steps, each one short. Nothing here writes outside the folder you point it at.

  1. Install the binary.
  2. Write your first script: jess init, one file, jess run.
  3. Build your first package: a manifest, a module, a test, a command target, packed and run.
  4. Set up your editor with the types, in VS Code, Neovim, Zed, or Helix.

Then Scripting explains how the pieces fit, and the API and CLI references are for looking things up.

Install Release archives, cargo install, PATH setup, shell completions, man pages, upgrading, and uninstalling. Your First Package A manifest, a module, a test, and a command target, written by jess init; inspected, tested, type-checked, run, packed, and run again from the JPK. Editor Setup Types, completion, and strict checking for jess scripts in VS Code, Neovim, Zed, and Helix: what jess init writes, and how to do it by hand.