fix: prevent [object Object] error display in console output #1
+6
−6
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
Fix the issue where running opencode displays
[object Object]instead of meaningful error messages.Root Cause
Multiple locations in the codebase were passing objects directly to
console.error()orconsole.log(), which causes JavaScript to convert objects to the string[object Object].Changes
packages/opencode/src/index.ts: Convert error to string using conditional checkpackages/opencode/src/cli/cmd/github.ts: Properly format error objects before loggingpackages/opencode/src/cli/cmd/debug/file.ts: Use JSON.stringify for object outputTesting
The fix ensures that error messages are properly displayed instead of
[object Object].Co-Authored-By: Claude [email protected]