tibetan-calendar-temporal 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,6 +4,12 @@ Compute Tibetan calendar dates in JavaScript — leap months, doubled and skippe
|
|
|
4
4
|
year names and observances — for almanac applications, practice calendars, and anything that has to
|
|
5
5
|
show a Tibetan date and be right about it.
|
|
6
6
|
|
|
7
|
+
It computes two calendars: **Phugpa**, the Men-Tsee-Khang standard and the basis of the almanacs most
|
|
8
|
+
practitioners use, which is the default; and the **Bhutanese** calendar of the Royal Government of Bhutan.
|
|
9
|
+
The **Tsurphu** (Karma Kagyu) and **Mongolian** calendars are **not included**: the engine can express
|
|
10
|
+
them as configuration, but neither has been checked against an almanac of its own — see
|
|
11
|
+
[Traditions](#traditions).
|
|
12
|
+
|
|
7
13
|
```sh
|
|
8
14
|
npm install tibetan-calendar-temporal
|
|
9
15
|
```
|
|
@@ -57,7 +63,7 @@ see [why you can trust these dates](docs/why-trust-these-dates.md).
|
|
|
57
63
|
| **Names in three renderings** | Tibetan script, Wylie, and THL Simplified phonetics (with eleven recorded corrections) for every weekday, element, gender, animal and rabjung year — each checked by machine against independent sources before it shipped |
|
|
58
64
|
| **Observances** | The great holy days and the monthly cycle, as configurable rules. Each result says *how* it landed on its day, so a display can show the almanac's footnote instead of presenting a moved date as an exact one |
|
|
59
65
|
| **Astrological attributes** | What kind of day it is, not just which day: the year's five elements, the month's and lunar day's labels, the calendar day's own, and the elemental yoga — which needs the moon's real position, not a cycle. A separate subpath, sourced piece by piece |
|
|
60
|
-
| **
|
|
66
|
+
| **Two calendars, four configs** | Phugpa and Bhutanese, each in two parameterisations. Constants and rules are injected as data, so a further tradition is a config object rather than a code change; Tsurphu and Mongolian are expressible that way but not shipped, because no almanac has checked them |
|
|
61
67
|
| **Date arithmetic** | Add days or months, count between two dates, find the next true full or new moon, and reduce a month to one sortable integer for a database key |
|
|
62
68
|
| **Fast, and computed rather than looked up** | No date tables, no network, nothing asynchronous: every answer is integer arithmetic done on the spot, identical on every platform. On a 2026 laptop a conversion takes about 7 µs, a month grid about 0.14 ms and a year of observances in 2–3 ms, so it can run in a render path — [measured, with the machine](https://github.com/nyamlen/tibetan-calendar-temporal/blob/main/bench/RESULTS.md#re-recorded-2026-11-18) |
|
|
63
69
|
|
|
@@ -412,10 +418,12 @@ back-projection is worse than the headline rate suggests. All three counts are r
|
|
|
412
418
|
engine and asserted in `test/computation/conversion.test.ts`. The evidence for the default is in
|
|
413
419
|
[docs/decisions/2026-08-12-lunar-anomaly-a2-default.md](https://github.com/nyamlen/tibetan-calendar-temporal/blob/main/docs/decisions/2026-08-12-lunar-anomaly-a2-default.md).
|
|
414
420
|
|
|
415
|
-
**
|
|
416
|
-
|
|
417
|
-
|
|
418
|
-
project exists to avoid — not because the
|
|
421
|
+
**Two other versions are not shipped: Tsurphu** (*mtshur phu*), the Karma Kagyu system, **and the
|
|
422
|
+
Mongolian** calendar, used in Mongolia and by the Buryats and Tuvinians. Neither ships because nothing
|
|
423
|
+
here has been validated against an almanac of its own, and an unvalidated calendar published with
|
|
424
|
+
this library's authority is exactly the failure this project exists to avoid — not because the
|
|
425
|
+
algorithm cannot express them. For a Mongolian date today, `@hnw/date-tibetan` is the shortest
|
|
426
|
+
route; see [when to use which](https://github.com/nyamlen/tibetan-calendar-temporal/blob/main/docs/other-implementations.md).
|
|
419
427
|
|
|
420
428
|
It can. Every astronomical constant is injected through a `TraditionConfig` rather than hardcoded,
|
|
421
429
|
including the scaling denominator, which is *derived* from the constants rather than fixed — Phugpa
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "tibetan-calendar-temporal",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "Tibetan calendar computation engine built on Temporal — the Phugpa and Bhutanese traditions, with the Tsurphu and Mongolian variants addable as config.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|