Skip to main content
Keja has two kinds of failure. A bad request returns a framework error as JSON and the process keeps serving. A bad project file prints a project error. keja dev keeps the last good project and waits. keja start exits. A request that fails inside a route returns JSON. The body is the framework error plus any extra fields, such as Zod issues. These responses are not printed by the CLI. frameworkErrors exports the same objects. A failure while loading the project throws ProjectError. The CLI prints a red ERROR badge, the scope Project, the code, the name, the detail, the description, and the tip. keja dev then waits. keja start exits 1.