Languages and monorepo tools
Putnami runs a workspace through extensions: one per language, and one per monorepo tool a repository already uses. This page lists each of them with the reference that documents it. The status column is read from the reviewed support catalog every time the site is built; what each status commits to, and what a missing one means, is on Support status.
Languages
TypeScript, Go and Python run on full extensions: Putnami scaffolds their
projects from its templates and runs them with its own jobs. Each other
language runs on a stack extension, which runs the tools the repository
already uses and reads the repository the way putnami observe does.
| Language | Extension | Status |
|---|---|---|
| TypeScript | @putnami/typescript |
Stable |
| Go | @putnami/go |
Stable |
| Python | @putnami/python |
Experimental |
| Dart and Flutter | @putnami/dart |
Experimental |
| .NET | @putnami/dotnet |
Experimental |
| Java and Kotlin | @putnami/java |
Experimental |
| PHP | @putnami/php |
Experimental |
| Ruby | @putnami/ruby |
Experimental |
| Rust | @putnami/rust |
Experimental |
| Swift | @putnami/swift |
Experimental |
Monorepo tools
A monorepo tool integration turns each project of a repository built with
that tool into a Putnami project. Putnami selects what a change affects and
gives the verdict; who runs each task and whose cache answers depends on the
tool, and on the mode the repository adopts it in.
Adopt Putnami on an existing monorepo
walks each tool through putnami init --from <tool>.
| Tool | Extension | Status |
|---|---|---|
| Bazel | @putnami/bazel |
Experimental |
| moon | @putnami/moon |
Experimental |
| Nx | @putnami/nx |
Experimental |
| Pants | @putnami/pants |
Experimental |
| Rush | @putnami/rush |
Experimental |
| Turborepo | @putnami/turbo |
Experimental |