Unhandled commands: bun test, bunx tsc, bun, bun run, bun drizzle-kit

Unhandled Commands

Discovered via rtk discover in a TypeScript/Bun backend project.

Command	Count	Example
`bun test`	34	`SMS_PROVIDER=console bun test src/modu..`
`bunx tsc`	12	`bunx tsc --noEmit 2>&1`
`bun`	6	`bun --env-file=.env.test test tests/st..`
`bun run`	3	`bun run tsc --noEmit 2>&1`
`bun drizzle-kit`	1	`bun drizzle-kit generate 2>&1`

Expected behavior

RTK should intercept and filter output for these Bun-specific commands the same way it handles npm test, tsc, etc.

Environment

Runtime: Bun
Project type: TypeScript backend (Elysia + Drizzle ORM)

wshm · Automated triage by AI

🔍 Automated Triage


✨ Category	`feature`
🟡 Priority	`medium`
🎯 Confidence	88%

Summary

Add RTK intercept/filter support for Bun runtime commands (bun test, bunx tsc, bun run, bun drizzle-kit); straightforward registry addition similar to existing npm/tsc handlers.

This looks like a simple fix that could be auto-resolved. Repo maintainers can use /wshm fix to attempt it.

Triaged automatically by wshm · This is an automated analysis, not a human review.

I am working on a fresh implementation against current develop. I will cover the reported Bun forms (bun test, option-prefixed bun, bun run, bun script shortcuts, and bunx) while preserving the underlying Bun/Bunx executable, with focused rewrite and output-filter tests.

Navigation Menu

Repository navigation

Unhandled commands: bun test, bunx tsc, bun, bun run, bun drizzle-kit #1316