cdate

Reproducible date formats for correspondence.

Format a Gregorian calendar date without a timezone, operating-system locale, or network dependency. The same inputs produce the same text in Rust, JavaScript, Python, and Typst.

import { longDate } from '@corbet-labs/cdate';

longDate('de-ch', 2026, 9, 7);
// 7. September 2026

Install

The 0.3.3 JavaScript distribution includes compiled ESM, CommonJS, TypeScript declarations, and a standalone browser module. Node.js 20+ is supported; no TypeScript loader is required.

// CommonJS
const { longDate } = require('@corbet-labs/cdate');

<script type="module">
  import { longDate } from 'https://cdn.jsdelivr.net/npm/@corbet-labs/cdate@0.3.3/dist/browser.js';
  console.log(longDate('de-ch', 2026, 9, 7));
</script>

Python 3.10+ packages are available on PyPI. See the installation guide for CLI commands and other distribution options. JSR publication and Typst availability are listed there explicitly.

Rust

use cdate::{long_date, month_year};

assert_eq!(long_date("de-ch", 2026, 9, 7).as_deref(), Some("7. September 2026"));
assert_eq!(month_year("en", 2026, 9).as_deref(), Some("September 2026"));

Typst in Rust hosts

The crate also ships the Typst package. Applications that embed the Typst compiler can register it from cdate::typst instead of downloading or vendoring a copy, so Rust and Typst always come from the same release. FILES holds package-relative paths (typst.toml, typst/date.typ, …) with their bytes; spec() is the import specification.

use cdate::typst::{FILES, NAME, NAMESPACE, VERSION, spec};

assert_eq!((NAMESPACE, NAME), ("preview", "cdate"));
assert_eq!(spec(), format!("@preview/cdate:{VERSION}"));
for (path, bytes) in FILES {
    // Serve `bytes` for `path` inside the package `spec()` in your Typst world.
    let _ = (path, bytes.len());
}

Documents then import the package as usual, for example #import "@preview/cdate:0.3.3": long-date.

Python

from cdate import long_date

assert long_date("de-ch", 2026, 9, 7) == '7. September 2026'

API

The ten date-table entries are de, de-at, de-ch, de-li, en, en-gb, en-us, fr, it, and rm. Matching is case-insensitive; other locales fall back through the base language to English. Impossible calendar dates return null/None. Inputs are calendar components, not timestamps. Other family libraries have broader locale coverage.

Correspondence family

Development

Behavior is defined by the locale tables and shared conformance vectors. Rust, JavaScript, and Python run the same vectors. Selected CI checks exercise installed JavaScript tarballs, Python wheels and command-line entrypoints, and Typst packages. Release validation records the actual runtime and platform; Linux results do not establish native Windows or macOS coverage. All five Rust crates forbid unsafe code in their own source.

See the release guide for generation, verification, and publication commands.

License

Copyright 2026 Julian Y. Richard Corbet. The 0.3.3 release line is licensed under LGPL-3.0-only WITH LGPL-3.0-linking-exception, with the incorporated GPL version 3. Combined works may link statically or dynamically without relinking duties; library modifications stay LGPL. Applications can use a different license subject to the LGPL's conditions. Previously released and already prepared distributions retain their original grants. The installation examples above refer to those available releases; 0.3.3 is published to registries.

See the licensing notes for distribution conditions and retained notices. Contributions are subject to the Contributor License Agreement.