Problem
resolveEntrypointPath in cli.js has an empty catch {} block that silently swallows fs.realpathSync failures. If the file doesn't exist or permissions are wrong, the fallback to path.resolve masks the real issue, making startup failures hard to debug.
function resolveEntrypointPath(filePath) {
if (!filePath) return null;
try {
return fs.realpathSync(filePath);
} catch {
return path.resolve(filePath); // silently masks real errors
}
}
Proposed Fix
Log the error to stderr before falling back:
catch (error) {
process.stderr.write(`resolveEntrypointPath: realpathSync failed for ${filePath}: ${error.message}\n`);
return path.resolve(filePath);
}
Context
Found during PR #18 review by silent-failure-hunter agent.
🤖 Generated with Claude Code
Problem
resolveEntrypointPathincli.jshas an emptycatch {}block that silently swallowsfs.realpathSyncfailures. If the file doesn't exist or permissions are wrong, the fallback topath.resolvemasks the real issue, making startup failures hard to debug.Proposed Fix
Log the error to stderr before falling back:
Context
Found during PR #18 review by silent-failure-hunter agent.
🤖 Generated with Claude Code