The same way that a "JAMstack" static site generator like Hexo, Jekyll, etc that requires some additional Runtime Cₙ, Cᵣ (or binary B or so on) helps you generate a static website from Markdown—except you're using a static site generator that instead targets the Runtime A (i.e. Firefox or Chrome or whatever browser you want) that we have quietly assumed is already available and is going to be used at some point, anyway.
From <https://news.ycombinator.com/item?id=24495646>:
> [There is] a "packager" for putting together add-ons. It uses "node.js". All it really does is apply "zip" to some files. I tried to install the "packager" on Ubuntu 18.04 LTS. It had several hundred dependencies, and wouldn't run because of some version dependency in node.js for something totally irrelevant to the task at hand
From <https://news.ycombinator.com/item?id=28518839>:
> If folks were really committed to improving the developer experience, [...] development would work like this: ¶1. Download the project source tree ¶2. Open README.html ¶3. Drag and drop the project source onto README.html
See also: <https://news.ycombinator.com/item?id=28407936>