knip fails on main: 9 unused exports under modes/rpc/machine-op
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- tooling
Research direction
Reproduce with bun run knip:check from the repo root, then open the files under packages/coding-agent/src/modes/rpc/machine-op/ at the listed line numbers (handler.ts:42, live-handle.ts:11-12, machine-terminals.ts:14, op-args.ts:17, real-path.ts:26,63, terminal-input.ts:8, wire.ts:20). For each name, drop the export keyword, or leave it and add a real consumer such as a test that pins the limit. Done is a clean knip run; the ./dist/bedrock-provider.js entry in packages/ai/knip.jsonc is a separate optional hint.
Written by the indexing model from the issue text.
Description
Summary
bun run knip:check fails on main with 9 unused exports, all under packages/coding-agent/src/modes/rpc/machine-op/:
handler.ts:42RELAY_HOST_READ_MAX_BYTESlive-handle.ts:11OUTPUT_SETTLE_MS,:12RETAINED_OUTPUT_BYTESmachine-terminals.ts:14MACHINE_TERMINALS_MAXop-args.ts:17READ_RANGE_MAX_BYTESreal-path.ts:26realPathUnder,:63withinterminal-input.ts:8KEY_GAP_MSwire.ts:20MACHINE_OP_COMMANDS
knip also hints that ./dist/bedrock-provider.js can be removed from ignoreUnresolved in packages/ai/knip.jsonc.
Expected
knip is clean. Each name is un-exported, or used by a real consumer (for example a test that pins a limit) where that consumer needs it.
Related
Found while verifying #6809 (#6807), which fixes the two knip items #6767 left; these 9 come from a different change.
- Dominant language
- TypeScript
- Stars
- 517
- Forks
- 163
- Avg merge
- 23h 31m
- Merged PRs (30d)
- 700
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from code-yeongyu/senpi
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
code-yeongyu/senpi#6746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
code-yeongyu/senpi#6742 ·
Maintainers usually reply within 1 day
-
host ensure fails with EACCES for a second OS user: senpi-rpc-host-locks is shared across usersOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
code-yeongyu/senpi#6738 · 1 comment ·
Maintainers usually reply within 1 day
-
[review-low] code-yeongyu/senpi#6726: glob error text for plain and '..' patterns, and UNC prefixesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
code-yeongyu/senpi#6734 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
code-yeongyu/senpi#6723 ·
Maintainers usually reply within 1 day
All issues in code-yeongyu/senpi
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langchainjs#12239 ·
Maintainers usually reply within 1 day
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
paperclipai/paperclip#21837 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 93/100
lingdojo/kana-dojo#34169 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100