Skip to content

devlanes is in beta and not ready for production use.Report an issue

pnpm workspace with turbo and a second project

A pnpm workspace scaled down from a SaaS monorepo: a Hono API and two Vite apps in apps/, two shared packages in packages/ that turbo builds, and a billing app in apps/billing that is a devlanes project of its own. The lane’s values are part of turbo’s cache key, and the two projects read each other’s URLs.

  • devlanes, with devlanes setup run once
  • Node 22.12 or later and pnpm 11
Terminal window
cd workflows-pnpm-monorepo
devlanes start

devlanes start --no-ui prints the start as text:

example-pnpm-monorepo@0 (main): 3/3 ready
ready api http://127.0.0.1:20581 https://api.example-pnpm-monorepo.localhost
ready web http://127.0.0.1:20582 https://example-pnpm-monorepo.localhost
ready admin http://127.0.0.1:20580 https://admin.example-pnpm-monorepo.localhost

Open https://example-pnpm-monorepo.localhost. The page lists the accounts it fetched from https://api.example-pnpm-monorepo.localhost and links to https://admin.example-pnpm-monorepo.localhost and to the billing app. Until a lane of the billing project runs, the billing row says no lane of example-pnpm-billing runs.

  1. install runs pnpm install --frozen-lockfile for the whole workspace.
  2. build-deps runs the root build-deps script, turbo run build --filter=./packages/*: tsc compiles @acme/config and @acme/ui into packages/*/dist, which the apps import. Both tasks have when: lane.create, so they run on a lane’s first start until they succeed once, and a fresh worktree needs only devlanes start.
  3. api extends the api template (tags: [api], a ready check on /healthz) and runs tsx watch src/index.ts in apps/api. It serves https://api.example-pnpm-monorepo.localhost and sends CORS headers to the origins in DEVLANES_ORIGINS.
  4. web and admin extend the web template (preset: vite, tags: [web], a ready check on /) and run vite in apps/web and apps/admin, on https://example-pnpm-monorepo.localhost and https://admin.example-pnpm-monorepo.localhost.

Every service points run_script.file at its own package.json, and devlanes runs the script with pnpm, from packageManager in the root package.json.

global_env sets the lane’s index and URLs as VITE_* on every service and task, and vite build copies them into the bundle: lane 1’s apps/web/dist calls https://api.example-pnpm-monorepo1.localhost. turbo.json lists VITE_* in globalEnv, so they are part of every task’s hash and a lane never replays another lane’s bundle. DEVLANES_* is in globalPassThroughEnv: turbo’s strict env mode hides variables it is not told about, and pass-through hands them to scripts without hashing them.

devlanes run build runs turbo run build with the lane’s environment. A second run in the same lane replays all six builds from the cache and ends with FULL TURBO. Run in the second lane from “Try next”, the packages hit the cache that lane’s build-deps filled and the apps rebuild:

build#8 @acme/ui:build: cache hit, replaying logs 09015a7624513ef7
build#10 @acme/config:build: cache hit, replaying logs c93795d22b939a00
build#12 @acme/admin:build: cache miss, executing b624b36fe97cbf66
build#13 @acme/web:build: cache miss, executing de9968b0fbbdd7b7
build#14 @acme/billing:build: cache miss, executing fb273c221a9a1c5e
build#15 @acme/api:build: cache miss, executing a63eeea76061d385

globalEnv applies to every task, so any change to a VITE_* value rebuilds packages/* too. Starting example-pnpm-billing changes VITE_BILLING_URL, and the next devlanes run build in lane 0 reported Cached: 0 cached, 6 total.

apps/billing/devlanes.yaml declares project: example-pnpm-billing. Commands run anywhere under apps/billing use it, the nearest devlanes.yaml, and the rest of the example uses the root one. example-pnpm-billing has its own lanes, ports and domain, example-pnpm-billing.localhost, and its relative paths start at apps/billing, so run_script.file: package.json is apps/billing/package.json. Its install task runs pnpm install from apps/billing, which installs the whole workspace, and its build-deps builds only what billing imports with turbo run build --filter=@acme/billing^....

The two projects read each other’s URLs through projects.<project>.services, with each dash in the project name written as an underscore:

VITE_BILLING_URL: ${{ projects.example_pnpm_billing.services.web.public_url | default('') }}

The value is set when the service starts and is empty while no lane of example-pnpm-billing runs. apps/billing/devlanes.yaml does the same in the other direction with projects.example_pnpm_monorepo.services.web.public_url.

  • Start the billing project: cd apps/billing && devlanes start. https://example-pnpm-billing.localhost shows This is lane 0 of example-pnpm-billing., three invoices and a link back to https://example-pnpm-monorepo.localhost.

  • Still in apps/billing, devlanes -p example-pnpm-monorepo restart web restarts the root project’s web, which now gets the billing URL, and the billing row on https://example-pnpm-monorepo.localhost becomes a link:

    Terminal window
    devlanes -p example-pnpm-monorepo env show web | grep VITE_BILLING_URL
    VITE_BILLING_URL=https://example-pnpm-billing.localhost
  • Start a second lane: git worktree add ../examples-checkout -b feat/checkout, then cd ../examples-checkout/workflows-pnpm-monorepo && devlanes start. The new worktree has no node_modules or packages/*/dist, and the lane.create tasks create them.

  • Without a worktree, devlanes lane new --name example-pnpm-monorepo-review --start adds lane 1 to the same folder. https://example-pnpm-monorepo1.localhost shows This is lane 1 of example-pnpm-monorepo. and 200 from lane 1 from https://api.example-pnpm-monorepo1.localhost.

  • cd apps/billing && devlanes lane new --name example-pnpm-billing-review --start does the same for billing on https://example-pnpm-billing1.localhost. Lanes added to one folder are all on main, and each lane 1 links to lane 0 of the other project.

  • From the example’s root, devlanes status lists the root project’s lanes and devlanes -p example-pnpm-billing status the billing project’s:

    example-pnpm-billing
    LANE BRANCH STATE SERVICES CPU MEM URL
    0 main running 1/1 0.0% 146.3 MiB https://example-pnpm-billing.localhost
    1 main running 1/1 0.0% 139.5 MiB https://example-pnpm-billing1.localhost
  • Edit the footer in packages/ui/src/Page.tsx and run devlanes run build-deps. turbo rebuilds @acme/ui (cache miss) and replays @acme/config, Vite logs hmr update /@fs/.../packages/ui/dist/Page.js, and https://example-pnpm-monorepo.localhost and https://admin.example-pnpm-monorepo.localhost show the new footer. So does https://example-pnpm-monorepo1.localhost, because lanes in one folder share packages/*/dist.

  • devlanes run typecheck runs tsc --noEmit in all six packages through turbo run typecheck, after building packages/*.

  • Remove the lanes: devlanes lane clean example-pnpm-monorepo-review --yes and devlanes lane clean 0 --yes here, then devlanes -p example-pnpm-billing lane clean example-pnpm-billing-review --yes and devlanes -p example-pnpm-billing lane clean 0 --yes.

  • devlanes.yaml: the root project, with the VITE_* lane values in global_env, the install, build-deps, typecheck and build tasks, the api and web templates and the services.
  • apps/billing/devlanes.yaml: the example-pnpm-billing project with its own install and build-deps and one service.
  • turbo.json: globalEnv and globalPassThroughEnv, and the build and typecheck tasks.
  • packages/config/src/index.ts: serverEnv(), pageEnv() and laneJson().
  • packages/ui/src/: the Page, Card and LaneCard components the Vite apps share.
  • apps/api/src/: the API, with /api/accounts, /lane and /healthz in app.ts.