TypeScript Test Commands
Root Commands
pnpm lint
pnpm lint:packages
pnpm typecheck
pnpm build:packages
pnpm test
pnpm test:e2e
pnpm test:e2e:node
pnpm test:e2e:cloudflare
pnpm test:e2e:cliPackage Focus
Use package filters for narrow checks:
pnpm --filter @composio/core test
pnpm --filter @composio/core typecheck
pnpm --filter @composio/<provider> test
pnpm --filter @composio/<provider> typecheckWhen To Use E2E
- Use Node/Cloudflare E2E for runtime packaging or module-resolution regressions.
- Use CLI E2E for CLI binary behavior and output contracts.
- Docker must be available for runtime and CLI E2E tests.
Test Placement
- Package tests live under
ts/packages/<package>/test/. - Runtime E2E tests live under
ts/e2e-tests/runtimes/. - CLI E2E tests live under
ts/e2e-tests/cli/.
CLI Effect v4 tests
ts/packages/cli tests run on effect@^4.1.0 and a matching @effect/vitest (both using matching ranges in pnpm-workspace.yaml). Read effect-v4-cli.md before writing or
porting a CLI test — it covers it.effect/layer(...) usage, explicit per-service test layers
(v4's Context.Service has no auto-generated .Default the way v3's Effect.Service did), and
the @effect/platform-bun subpath-import rule that keeps the Node-hosted Vitest runner from
loading BunRedis.