First Working Version of Kireji on NPM

Edited Feb 8, 2026 | Posted Feb 6, 2026 | ~2 minute read

Ever since I started the Kireji project, both the Kireji Web Framework and its flagship project (the Demo App Ecosystem which includes this notebook) have been one-and-the-same. The two projects were stuck together in one repo while I worked out what the end-user experience should be for other developers using the framework. Until those design questions could be answered, I didn't want to split them up too early and risk calcifying them both.

I published the kireji package on NPM six months ago but it was just a placeholder to retain the name. It wasn't until this week that I was finally able to publish the very first working version of the framework.

Finally, the time has come.

To prove the framework works, this demo project no longer has any of the core framework files and content. Instead, this project is bringing in the framework via NPM. None of the files in this repo are necessary for the framework to function; they only define the demo applications. This process felt more straightforward than I expected it to, probably because I've been slowly refining separation-of-concerns for some time and precisely inching my way towards this moment.

Although the framework can be used right now via npm install kireji and although this very notebook application and a handful of others are already using it, (and they all work), there is no documentation to guide developers on its core philosophy, getting set up for the first time, or navigating its many quirks. In addition, I expect to make major changes (including breaking changes) to the framework very frequently in the coming weeks. As a result, the framework is not ready for beta testing yet. Feel free to contact me (see my social links in the footer) if you're interested in trying it out, however.

I look forward to tackling the aforementioned concerns very soon, but for now, this is a major milestone!

As a side note, I published a note three days ago about the first app ecosystem that I deployed completely separately from the demo one. At the time, I copied and pasted the framework's files from the demo repo into that one. But now, it brings those files in via NPM just like this ecosystem does.