@edtf-ts/core - EDTF TypeScript and Fuzzy Dates
Dates, the Way Humans Mean Them
Modern TypeScript implementation of Extended Date/Time Format (EDTF) with temporal reasoning, fuzzy date comparison, and human-readable formatting.
Additive core operations provide canonical spelling, significant-year ranges, tagged finite/open/unknown bounds, lazy value enumeration, and an all-relations summary. Existing FuzzyDate methods and collection arrays remain available. Significant-digit bounds now cover the represented range (1950S2 means 1900–1999); invalid digit counts are rejected.
GitHub Repository | Documentation | Interactive Playground
Upgrading from 0.5.0 to 0.6.0
Existing exports remain available. The main risks to existing callers are:
- Datetime interval endpoints are rejected. Use
FuzzyDate.from()orparse()to handle validation failures. StandaloneDate.toISOString()timestamps remain accepted by default; milliseconds are preserved in bounds and ISO output. Strict mode excludes fractional seconds. compare()/.compareTo()now returnnumber | 'UNKNOWN'; numeric assignments and direct sort callbacks may need a TypeScript guard.sort(),earliest(),latest(), andFuzzyDate.compare()throw when mixing timezone-qualified timestamps with calendar dates or timezone-free datetimes.
The migration guide explains safe adaptations, result-type changes, and advanced relation callbacks. Update @edtf-ts/natural at the same time if you use it.
Why EDTF?
People don't experience time like computers do. We remember seasons, eras, and approximate moments. We say "around," "before," "after," and "sometime between."
Yet most software insists on rigid ISO 8601 dates, forcing humans to pretend they know more than they do. When software only accepts exact dates, users are forced to guess, invent, or leave fields blank—losing valuable information.
EDTF exists because real time is messy—and pretending otherwise loses information.
Features
- FuzzyDate API - Temporal-inspired, method-based interface with IDE autocomplete
- EDTF Levels 0, 1, and 2 - Strict profile validation with a source-linked conformance corpus
- TypeScript-first - Complete type safety with discriminated unions
- Allen's interval algebra - 13 temporal relations with four-valued logic
- Human-readable formatting - English, Spanish, and French phrases, including qualifiers, collections, seasons, and ages
- Zero runtime dependencies - Lightweight and fast
- BigInt support - Handle extreme historical dates beyond JavaScript Date limits
- Tree-shakeable - Import only what you need
Localized Output
import { FuzzyDate } from '@edtf-ts/core';
const date = FuzzyDate.parse('1870-03-12');
date.format({ locale: 'es-ES' }); // '12 de marzo de 1870'
date.format({ locale: 'fr-FR' }); // '12 mars 1870'
Rendering defaults to en-US. When passing a locale to @edtf-ts/natural, make sure its language matches the input, or set language explicitly. The playground starts with your browser’s locale and offers one top-level override for all parsing and rendering. See the migration guide for compatibility details.
Installation
npm install @edtf-ts/core
# or
pnpm add @edtf-ts/core
# or
yarn add @edtf-ts/core
Quick Start
import { FuzzyDate } from '@edtf-ts/core';
// Parse EDTF strings into FuzzyDate objects
const date = FuzzyDate.parse('1985-04-12');
const interval = FuzzyDate.parse('2004-06/2006-08');
const uncertain = FuzzyDate.parse('1984?');
const decade = FuzzyDate.parse('198X'); // Any year 1980-1989
// Method-based API with IDE autocomplete
date.format(); // "April 12, 1985"
date.isBefore(interval); // 'YES'
uncertain.isUncertain; // true
decade.hasUnspecified; // true
// Temporal comparison with four-valued logic
const a = FuzzyDate.parse('1985');
const b = FuzzyDate.parse('1990');
a.isBefore(b); // 'YES' - definitely before
a.during(b); // 'NO' - not contained within
a.overlaps(b); // 'NO' - no time overlap
// Handle uncertainty honestly
const year = FuzzyDate.parse('1985');
decade.equals(year); // 'MAYBE' - could be 1985
// Boolean convenience methods for when you need true/false
a.isDefinitelyBefore(b); // true
decade.isPossiblyBefore(year); // true (could be 1980-1984)
EDTF Specification Support
Level 0 (ISO 8601 Profile)
- Calendar dates:
1985-04-12 - Reduced precision:
1985-04,1985 - Date/time:
1985-04-12T23:20:30 - Intervals:
1985/1990,1985-04-12/1985-04-15
Level 1 (Extended)
- Uncertain/approximate:
1984?,1984~,1984% - Unspecified digits:
199X,19XX,1985-XX-XX - Extended intervals:
1984?/2004~,../1985,1985/.. - Years exceeding 4 digits:
Y170000002 - Seasons:
1985-21(Spring),1985-22(Summer)
Level 2 (Partial Uncertainty)
- Component-level qualification:
?2004-06,2004-~06,2004-06-~11 - Partial unspecified:
156X-12-25,15XX-12-25 - Sets/Lists:
[1985,1990,1995],{1985-04,1985-05} - Extended seasons:
1985-25(Winter, Northern)
Compact year sets and lists
compactYearRanges(parsedValue) returns compact EDTF such as [1667..1668,1670..1672] from [1667,1668,1670,1671,1672]. It merges adjacent exact years in their existing order, retaining gaps, duplicates, open bounds, and set/list meaning. Other precisions and qualified years remain separate. The original parsed object and its edtf stay unchanged.
formatHuman uses concise year ranges in English, Spanish, and French. For example, [1870..1880] renders as One of: 1870 through 1880, Una de estas fechas: 1870 a 1880, or Une de ces dates: 1870 à 1880.
Truth Values in Comparison
The comparison methods use four-valued logic for precise temporal reasoning:
- YES - Relationship definitely holds
- NO - Relationship definitely does not hold
- MAYBE - Relationship might hold (uncertain due to imprecision)
- UNKNOWN - Cannot determine (missing information)
const y1980 = FuzzyDate.parse('1980');
const y1990 = FuzzyDate.parse('1990');
const decade = FuzzyDate.parse('198X');
y1980.isBefore(y1990); // 'YES' - bounds prove it
decade.equals(y1985); // 'MAYBE' - could be 1985
// Boolean convenience methods
y1980.isDefinitelyBefore(y1990); // true
decade.isPossiblyBefore(y1985); // true
Documentation
Full documentation is available at bobpritchett.github.io/edtf-ts
Related Packages
- @edtf-ts/natural - Natural language date parsing ("circa 1950", "early January 1985")
License
MIT Copyright 2025 Bob Pritchett
Contributing
Contributions welcome! See the GitHub repository for details.
Interoperability profile
parse(input, { level: 2, conformance: 'strict' }), isValid, and FuzzyDate.from / FuzzyDate.parse support the strict interoperability profile. Extended support is the default. Season interval endpoints are a supported extension; strict mode excludes season endpoints, season collection members, and qualified seasons. Qualified calendar-date collection members remain supported. Human formatting preserves explicit enumeration/range structure, including month/day ranges. See interoperability and migration.