I built a JSON CLI tool with Bun and TypeScript — here's what actually happened

<h3> The Problem That Started It All </h3> <p>It was 3 AM, and I was staring at yet another ChatGPT conversation, manually copying files from my project one by one. "Here's

<p>I needed to decode a JWT last week. I searched, clicked the first result, and got a login wall. The second site wanted me to "create a free account" to see my own token's

<h2> I Built an npm CLI Tool That Checks If Your Project Is Deployment Ready </h2> <p>Deployments often fail for the smallest reasons.</p> <p>A missing <code>.env</code> file.<br

<p>Everything looked perfect.</p> <p>I had <code>mcporter 0.7.3</code> configured with the Exa MCP server:<br /> </p> <div class="highlight js-code-highlight"> <pre

<p>If you work with APIs every day, you've probably had this experience.</p> <p>You copy a JSON response from your browser's DevTools...</p> <p>...and you're greeted by a single

<p>Somewhere in the middle of building <a href="https://github.com/GauravS13/KilnForge" rel="noopener noreferrer">KilnForge</a>, we wrote a fully working feature, tested it,