Replace `date-fns` by `date-and-time-formatter`
Fixes #436
Backwards-compatible because date-fns follows Unicode LDML too (well, more or less https://blog.date-fns.org/v2-unicode-tokens/)
coverage: 99.197%. remained the same when pulling 28f51aee5228f1090b5b2aae1f572e73b8e700e9 on replace-date-fns-by-date-and-time-formatter into a61ef39468c82b66ebb247a5a5e2cf479a0c4def on main.
date-fns pushed a breaking change and we're having issues in our projects.
It would be helpful to either upgrade to date-fns to the latest or to replace it entirely (based on this PR). We've set resolutions in our package.json (we use yarn) for now, but I always forget to remove them and it's gonna bite future us right before something important, you know, like when most these things tend to rear their heads.
Thanks everyone!!
Hey! This is now fixed in v9.0.0. https://github.com/open-cli-tools/concurrently/releases/tag/v9.0.0