-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix: remove debug console.log statements from plugin commands and targets #890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,7 +51,6 @@ export default defineCommand({ | |
|
|
||
| // Plugin path goes to stdout (for scripting); usage hint goes to stderr | ||
| console.error(`\nReady. Use with:\n claude --plugin-dir ${pluginPath}\n`) | ||
|
Comment on lines
52
to
53
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When Useful? React with 👍 / 👎. |
||
| console.log(pluginPath) | ||
| }, | ||
| }) | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For workspaces that do contain plugin manifests, this command now builds
pluginsand then exits without printing anything, sobun run ... listalways has empty stdout. That breaks the command's purpose and the existing CLI coverage intests/cli.test.ts, which expects a temp workspace withplugins/demo-plugin/.claude-plugin/plugin.jsonto outputdemo-plugin.Useful? React with 👍 / 👎.