Monorepos

⚠

True monorepo tooling — Turborepo, Nx, and workspaces with shared packages — is not yet supported and is actively in development. If your app depends on shared packages from sibling directories in the same repo, it may not build correctly. Support for Turborepo and Nx is coming soon.

If your repository contains multiple apps or packages, you can tell Jetpacked which subdirectory contains the app you want to deploy. The detection engine will analyse that subdirectory instead of the repo root.

Setting a subdirectory

When creating a new project, there's an optional App subdirectory field. Enter the path to your app relative to the repo root:

apps/web
packages/api
frontend

You can also change it later from Settings → General.

How it works

Jetpacked clones the full repository but runs detection and builds from inside the subdirectory you specify. The Dockerfile and build context are scoped to that path, so dependencies and config files in sibling packages are not included unless your build process explicitly references them.

One project per app

Each Jetpacked project deploys one app. If your monorepo has multiple apps you want to deploy, create a separate project for each one pointing to its subdirectory.

AI-generated monorepos

Tools like Lovable and some Claude Code setups sometimes produce a repository with a frontend and backend in separate folders. If Jetpacked doesn't detect your stack correctly from the root, setting the subdirectory is usually the fix.