Skip to content

fix(dev): restore tsconfig and fix tsx resolution for dev scripts#2073

Open
evanjacobson wants to merge 2 commits intomainfrom
fix/dev-scripts-post-monorepo
Open

fix(dev): restore tsconfig and fix tsx resolution for dev scripts#2073
evanjacobson wants to merge 2 commits intomainfrom
fix/dev-scripts-post-monorepo

Conversation

@evanjacobson
Copy link
Copy Markdown
Contributor

Summary

After the monorepo restructure (#1315), pnpm dev:start fails because tsx can't find a tsconfig when running dev scripts from the repo root — the root tsconfig.json and tsconfig.scripts.json were moved to apps/web/ without replacements.

This adds a minimal root tsconfig.json scoped to dev/**/* and scripts/**/*, plus a tsconfig.scripts.json alias for backward compatibility. It also fixes two related issues:

  • Bare tsx unreachable in tmux — commands sent into tmux panes used bare tsx, which isn't on PATH without pnpm's node_modules/.bin augmentation. Changed to pnpm exec tsx.
  • Stale docker-compose paths in kiloclawdev-start.sh still referenced the pre-restructure apps/web/dev/docker-compose.yml path instead of dev/docker-compose.yml.

Verification

  • pnpm typecheck passes
  • pnpm exec tsx dev/local/dashboard.tsx runs successfully with core and kiloclaw services
  • pnpm dev:start / pnpm dev:stop lifecycle works

Visual Changes

N/A

Reviewer Notes

The root tsconfig.scripts.json exists because tsx caches the tsconfig filename in the TSX_TSCONFIG_PATH env var, which can persist across tmux sessions from before the restructure. It's a one-line extends — zero maintenance cost.

@evanjacobson evanjacobson marked this pull request as ready for review April 6, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant