Building a Single-File Offline Prompt Tool With Vanilla JS
There's a quiet joy in shipping a tool as one file. No npm install, no build step, no deploy pipeline, no backend to keep alive. You double-click an HTML file and it works — on any OS, offline, forever. Here's the architecture I used to ship a 3,000-entry prompt tool this way, and why vanilla JS is underrated for this class of product.
Why single-file at all
The constraints force good decisions. When everything — markup, styles, logic and data — lives in one file, you can't reach for a dependency casually. You end up with something small, fast, and portable enough to sell as a download that runs anywhere.
The tradeoff: no ecosystem. No React, no component library, no bundler niceties. For a focused tool, that's fine. You don't need a virtual DOM to render a filterable list.
