Support built-in commands for Node.js runners and Pip#9
Conversation
- Update detectors to run built-in commands directly (e.g. `npm install` instead of `npm run install`) - Add list of built-in commands for npm, yarn, pnpm, bun, and pip - Update tests to reflect new behavior
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This PR improves the command generation for Node.js runners (npm, yarn, pnpm, bun) and Python's pip runner.
Previously,
runwould wrap all commands inrun(e.g.npm run install), which caused issues for built-in commands likeinstallthat are not scripts.Now,
runchecks if the task is a known built-in command and executes it directly if so.For pip, it now generates
python -m pip <task>for pip commands (likeinstall,list) andpython -m <task>for others.PR created automatically by Jules for task 17896635186105742915 started by @insign