I built this for a product planning tool (https://plan.fyi) I have been working on where I wanted users to define timelines using fuzzy language. My initial instinct was to integrate an LLM and call it a day, but I ended up building a library instead.
Existing date parsers are great at finding dates in text, but I needed something built for extracting context, understanding business time (EOD, COB, business days), parsing durations, and handling fuzzy periods like Q1 or "early january" or "Jan to Mar" etc.
It returns typed results (date, duration, span, or fuzzy period) and has an extract() function for pulling multiple time expressions from a single string - useful for parsing meeting notes or project plans.
I built this for a product planning tool (https://plan.fyi) I have been working on where I wanted users to define timelines using fuzzy language. My initial instinct was to integrate an LLM and call it a day, but I ended up building a library instead.
Existing date parsers are great at finding dates in text, but I needed something built for extracting context, understanding business time (EOD, COB, business days), parsing durations, and handling fuzzy periods like Q1 or "early january" or "Jan to Mar" etc.
It returns typed results (date, duration, span, or fuzzy period) and has an extract() function for pulling multiple time expressions from a single string - useful for parsing meeting notes or project plans.
https://timelang.dev (interactive playground)