Unhandled commands: bun test, bunx tsc, bun, bun run, bun drizzle-kit · rtk-ai/rtk#1316

(1 留言) (2 反應) (0 負責人)Rust (48,085 star) (2,914 fork)batch import

effort-smallenhancementgood first issue

描述

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`

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

技術棧: rusttypescript
領域: clideveloper experience
議題類型: feature
難度: 3
預計時間: 1-3 hours
活動狀態: fresh
清晰度: clear
前置要求: Rust knowledgeRTK source code structureCommand output filtering patterns
新手友善度: 60
研究方向: Examine how RTK currently intercepts and filters output for commands like 'npm test' and 'tsc' in the source code, likely in the command matching module. Add similar patterns for 'bun test', 'bunx tsc', 'bun', 'bun run', and 'bun drizzle kit'. Check the RTK configuration files for how command patterns are defined. The issue details commands and counts, so start by locating the existing command matching logic and adding entries for these bun variants.