rtk-ai/rtk

pnpm lint causing issue when ESLint isn't used

Open

#665 创建于 2026年3月17日

在 GitHub 查看
 (4 评论) (3 反应) (0 负责人)Rust (48,085 star) (2,914 fork)batch import
bugeffort-smallfilter-qualitygood first issue

描述

I have a project that uses pnpm and biome as linter. RTK seems to insist rewrite pnpm lint to rtk lint, which is then dependent on ESLint that I do not use. This causes the agent to get into a re-try loop. Despite several notes I provided in Agents.MD, the confusion seems big enough that the agents kept tripping over this. Sometimes it'd eventually figure out what to do.

Proof -

# Test RTK rewrite of pnpm lint
$ rtk rewrite "pnpm lint"
rtk lint

贡献者指南

技术栈
rust
领域
clitooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
understanding of pnpm lint semanticsfamiliarity with RTK's CLI rewrite logic
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the RTK source code, likely in the CLI rewrite module, to find where 'pnpm lint' is automatically rewritten to 'rtk lint'. Determine why it assumes ESLint is used and how to make the rewrite dependent on the presence of an ESLint configuration. Consider adding a check for ESLint config files (e.g., .eslintrc) before performing the rewrite, or allow users to opt out via a flag. Review any existing configuration in Agents.MD or related comments.