Repository navigation
Empty catch blocks silently swallow errors in config and initialization #11701
Description
Summary
Several empty catch blocks in the codebase silently swallow errors, making debugging difficult and hiding potential issues from users.
Locations
packages/opencode/src/config/config.ts:1235- Plugin resolution errors swallowedpackages/opencode/src/global/index.ts:53- Initialization errors swallowed- Multiple locations in file operations
Issue
1. Config plugin resolution (config.ts:1235)
for (let i = 0; i < data.plugin.length; i++) {
const plugin = data.plugin[i]
try {
data.plugin[i] = import.meta.resolve!(plugin, configFilepath)
} catch (err) {} // Error completely swallowed - user has no idea plugin failed
}2. Global initialization (global/index.ts:53)
try {
const contents = await fs.readdir(Global.Path.cache)
await Promise.all(
contents.map((item) => fs.rm(path.join(Global.Path.cache, item), {...})),
)
} catch (e) {} // Cache cleanup failure hiddenImpact
- Severity: Low-Medium
- Type: Error Handling / Debugging
- Effect:
- Invalid plugins silently ignored, user sees no feedback
- Initialization issues hidden
- Makes troubleshooting difficult
Suggested Fix
Replace empty catch blocks with proper logging:
// config.ts
try {
data.plugin[i] = import.meta.resolve!(plugin, configFilepath)
} catch (err) {
log.warn("failed to resolve plugin", { plugin, error: err })
// Optionally remove the invalid plugin from the array
}
// global/index.ts
try {
// ...cache cleanup
} catch (e) {
log.warn("failed to clear cache", { error: e })
}Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Feb 2, 2026
This issue might be a duplicate of existing issues. Please check:
These issues also address error handling gaps in the codebase that result in silent failures or crashes when errors aren't properly handled. You may want to review these related error handling issues to ensure a comprehensive solution across all affected modules.
github-actions commentedon Apr 3, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.