feat: track and expose component error/warning counts#35
Merged
Conversation
🦋 Changeset detectedLatest commit: 7027dd0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Store error and warning counts from UPDATE_ERRORS_OR_WARNINGS operations on ComponentNode. Add getComponentsWithErrorsOrWarnings() method to ComponentTree. Handle new 'errors' IPC command in daemon and enrich get-component responses with non-zero counts. Closes #19 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add formatErrors() formatter and errors CLI command to list components with non-zero error or warning counts. Annotate tree, search, and component output with warning/error indicators (e.g., ⚠2 ✗1). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Test UPDATE_ERRORS_OR_WARNINGS operation parsing, count storage and replacement, getComponentsWithErrorsOrWarnings(), tree node annotations, formatErrors(), and error annotations in formatTree/formatComponent. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update README, SKILL.md, and commands.md reference with the new errors command, annotation format, and examples. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
a6878b0 to
7027dd0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #19
Track and expose component error/warning counts from React DevTools protocol, enabling AI agents to quickly find components with errors.
Commits
02e8cf0ci: split CI into separate jobs for better visibility (ci: split CI into separate jobs for better visibility #29)303f9e4fix: Vite HMR broken when using reactDevtools() plugin (fix: Vite HMR broken when using reactDevtools() plugin #34)05090cafeat: surface specific changed prop/state/hook keys in profiling output (feat: surface specific changed prop/state/hook keys in profiling output #32)348b563feat: track and expose component error/warning counts32df76ffeat: add errors CLI command and error/warning annotations in output6e20550test: add tests for error/warning tracking and formattingcfcf39bdocs: document errors command and error/warning annotationsa7f6560chore: add changeset for error/warning counts featurea6878b0fix: ensure labels are assigned before errors commandChanges
errorsandwarningsfields toComponentNode, addederrorsIPC command typeUPDATE_ERRORS_OR_WARNINGSoperations, addedgetComponentsWithErrorsOrWarnings()methoderrorsIPC command with proper label assignmenterrorsCLI command to list components with non-zero error/warning countsTest plan
errorscommand returns components with error/warning counts🤖 Generated with Claude Code