@matthewmueller Owh forgot to mentioned one thing, it can also take any extra string in a natural sentence, and extract the time. For example if the input string is remind me to do laundry 2 hours later, it will automatically extract the substring with time.

For this, the CFG is suppressed as I mentioned, so what it does it do some preprocessing on the string (extract 2 hours later), and pass it to the original datejs parser.

Moreover, it can parse normal forms of date string, and e.g. '13 May 2011 01:30 UTC'.

The time extraction from arbitrary sentence is a pretty handle feature I think.

ahh sorry to leave you hanging on this @kengz! this looks great. thanks for your hard work. i'm going to merge this. let me know if you want me to release or if there's more to come before i should release.

regarding:

basically are the inconsistencies between my CFG and the original datejs.

i'm not sure if this is helpful or not, but i think it's usually pretty obvious what the date should be when you think about it, like "tomorrow morning" => some where around 9 or 10 the next day. so i wouldn't worry so much about breaking tests or existing implementation if you think the result will be more expected for folks.

I'll work on it a lil today, but my guess is the next update won't come through until at least next week. I'll let u know tonight if I can finish it? Otherwise assume I can't.

sure, no rush. loving these fixes :-)

hey @kengz, what's the state of this?

oh shoot, my github graph wasn't green for a long time, until recently. Nice timing.

Let's see what's left from last time:

• lodash dependencies were already completely removed, you can close started removing lodash to bring down the build size #76 ?
• activate full CFG
• update the tests and it's ok use new default times if it's reasonable (e.g. 7pm for evening)
• the issues stated in History.md
• attach doc and description for algo so people can understand it