funkpower
33441113ce
There is one engine and nine doors into it, and nothing until now checked that the doors agree. CI tested each binding against itself: the Python wheel imported, the C demo compiled, the npm package type-checked. None of that would have caught a field that crosses one boundary wrong, which is the failure this library is most exposed to, because a wrong answer about a fast day looks exactly like a right one. So: twelve days, chosen where the bindings could plausibly differ, and all twenty-two fields compared against what the command line says. The days are Pascha itself, the Nativity on both calendars, a Wednesday of the Great Fast under Byzantine Catholic law and again at the Typikon, a weekday of the Nativity Fast where Greek and Slavic usage part, the one Orthodox church on the Gregorian Paschalion, and a day with no feast. A release now runs what a push runs. It had been gated on cargo test alone, so the C ABI, the Lua binding, the Python parity check and the README examples were checked on the branch that led to a release and not on the release. Neither registry will reuse a version, so the gate belongs before the upload. Writing it found three things. The npm exports map did not expose the wasm by package path, so a bundler asked for typikon/web/typikon_bg.wasm was told no such path exists and had to reach into node_modules; the documented init() call was never affected. The suite could hang instead of fail, because the test web server was backgrounded inside a subshell and killed by job spec, leaving bash in do_wait forever. And pointing XDG_CONFIG_HOME at a path that does not exist isolates typikon and breaks every other program that keeps state under it, a browser included. A surface whose toolchain is missing is named as skipped, and fewer than three surfaces running is a failure rather than a pass, so a container with nothing installed cannot come out green.
typikon
The Orthodox liturgical day: feasts, seasons and the fast, computed rather than fetched. No network, no data files, no service to be up.
npm install typikon
import { today } from "typikon";
const day = today({ jurisdiction: "rocor" });
day.churchDate; // "5 September"
day.fast; // "xerophagy"
day.fastLabel; // "xerophagy — no oil or wine"
day.emoji; // the glyph for the level
day.title; // "The Holy Prophet Zachariah, father of the Forerunner"
day.season; // null in ordinary time
day.daysToPascha;
In a browser or a bundler, load the module first:
import init, { today } from "typikon";
await init();
const day = today({ jurisdiction: "rocor" });
Node needs no init, because it can read the WebAssembly itself. The exports
map picks the right build; typikon/node and typikon/web force one.
What comes back
A plain object, not a handle: the same document typikon --json emits, with
the same field names and the same stability promise. Nothing has to be freed
and JSON.stringify works on it. TypeScript types ship with the package.
The rest of it
import { describe, describeIso, week, pascha, jurisdictions } from "typikon";
describe(new Date(2026, 3, 12), { jurisdiction: "moscow" });
describeIso("2026-04-12", { jurisdiction: "moscow" });
week(new Date(), 7, { jurisdiction: "goarch" }); // seven consecutive days
pascha(2027, "old"); // 2027-05-02
jurisdictions(); // [{ key, name, note }, ...]
week reckons the year's movable cycle once rather than once a day, so it is
the thing to call for a calendar grid.
Which calendar
jurisdiction takes a church key, or a bare calendar where the church does not
matter: "old" (Julian throughout), "new" (Revised Julian fixed feasts with
the Julian Paschalion, the default) or "western" (Gregorian throughout,
Pascha included). jurisdictions() lists the rest. Two more options:
tradition,"slavic"or"greek", overriding the church's own usage. It moves fish in the Nativity Fast and the rank of the Protection.typikon: true, to show a day at the Typikon's full discipline rather than at the minimum a church's own particular law requires. What binds is reported either way, inbindsandobligation. This is for the Byzantine Catholic churches, whose law asks very much less than the tradition they keep.
Unlike the command line and the Python bindings, there is no remembered default: a browser has nowhere to keep one, so the default is the New Calendar and anything else is passed.
Accuracy
The Paschalion is exact. The fast follows the Typikon as the standard printed calendars apply it, which is the part where careful people differ; a parish calendar or a confessor overrides this, and neither is a bug report.
Licence
GPL-2.0-only. Source: https://git.pumpin.online/funkpower/typikon