I hand-rolled a PDF engine in vanilla JS so our invoice app needs zero dependenc

<p>A year ago I was rebuilding the same <code>&lt;PhoneInput&gt;</code> for the third time across three different projects. Each time I reached for

<p>PDF generation sounds boring until you're deep in archival standards, cryptographic signing, and cross-language memory bridges at 3am. Building <a

<blockquote> <p><strong>fulgur</strong> — <em>(noun, Latin)</em> lightning, flash of lightning.</p> </blockquote> <p>I've been building <a

<p>PDF generation is one of those problem spaces where the tooling is surprisingly rough for how common the use case is. I built DocuMint — a REST API for generating PDF invoices

<p>Every online image converter I tried had the same shape: drag your file in, it uploads to a server somewhere, you get a download link back.</p> <p>That's fine for a meme. It's

<p>Favicons are tiny but they matter. A sharp, recognizable 32×32 icon in a browser tab signals polish. But most favicon tools either require uploads, email sign-ups, or bloated

<p>I have a habit: any tool that says "processed locally, nothing uploaded" gets a packet capture before I believe it. This time it was PDF-to-image, and the count from picking a