rtk-ai/rtk

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

Open

#1,316 opened on Apr 14, 2026

View on GitHub
 (1 comment) (2 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-smallenhancementgood first issuehelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

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)

Contributor guide

Research direction
Investigate how RTK intercepts and filters output for npm/tsc commands, then replicate the pattern for bun test, bunx tsc, bun run, bun, and bun drizzle kit. Look for the handler mapping in the source code.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70