Packages
Tern packages.
Beyond the standard library: a web framework, database clients and the rest of a server. Any git repository can be a package too.
tern search WORD # find one
tern add roost # add it to tern.mod and fetch it
tern add geo GIT-URL # or any git repositoryFirst-party packages
Maintained with the language, written the way any package is. tern add NAME writes one to tern.mod and pins its exact files in tern.lock; an installed Tern carries a copy, so it works offline. The database ones come with Tern for now, because the runtime works closely with them: just import them.
grpc
A gRPC server (unary calls) over HTTP/2, in Tern: what OTLP/gRPC exporters and most unary clients need.
tern add grpcmigrate
Schema migrations for PostgreSQL and SQLite from numbered .sql files: up, down, status, locking
tern add migrateopenapi
OpenAPI 3.1 documents, Swagger UI and a typed TypeScript client from roost routes described with Tern types
tern add openapiqueue
A client for ternq, the message queue broker.
tern add queueroost
A web framework on the http engine: routing, middleware, WebSockets, SSE, static files, uploads, validation, rate limits, metrics
tern add roostsentry
Error reporting to Sentry: runtime errors with stack traces, request data, breadcrumbs
tern add sentrysqlgen
Typed Tern functions generated from SQL queries, checked against PostgreSQL or SQLite (like sqlc)
tern add sqlgenPublish your own
A package is a git repository with .tn files at the top. Push it, tag v0.1.0, and anyone can tern add it. There’s no account to create and nothing to upload. Fetching and building never run a package’s code, and every user sees what yours can reach (network, files, processes) before they accept an update that adds to it.