Make files-widget deps required and ship a release
Takeaway: Next time I'd open by stating upfront that bat/delta/glow are required, not optional, since that shaped most of the back-and-forth.
32 sessions on npm with a coding agent: the agent failed at least once in 13, and 17 finished without a human stepping in.
Takeaway: Next time I'd open by stating upfront that bat/delta/glow are required, not optional, since that shaped most of the back-and-forth.
Takeaway: Next time I'd just ask upfront to move npm's global prefix to my home directory instead of troubleshooting the EACCES error first — that's what actually fixed things for good.
Takeaway: Next time I'd open by asking the agent to check the actual runtime (Node vs Bun) and how extensions get resolved from npm before assuming the file: dependencies would just work — that mismatch cost most of the session.
Takeaway: Next time I'd start by pinning down the actual runtime types (like discovering args was a string, not an object) before mass-applying @ts-ignore everywhere — that shortcut created bugs we had to hunt down later.
Takeaway: Next time I'd ask directly for a Node-version-compatibility check before installing a new global CLI, since the crash turned out to be an ESM/extensionless-bin packaging issue rather than an install failure.
Takeaway: Next time I'd ask for spaced repetition, tags, stats, keyboard shortcuts, and duplicate-safe import/export all in the first prompt instead of adding them one round at a time, since each pass required re-reading the whole file.