I'm building date-fns MCP. I'm starting with documentation (per function doc, vectorized search) but have many more ideas.
What would you want to see in it?
๐ฅdate-fns v4.0 is out with first-class time zone support and no major breaking changes!
It's easy to use and has a minimal bundle footprint, with TZDateMini being just 761 B.
๐ฆธโโ๏ธWe believe in supporting our #opensource ecosystem and tools that enhance the development experience.
That's why we're excited to announce that #Reactadmin is now sponsoring @date_fns, the modern #JavaScript date utility library!๐ค
https://t.co/LZAG8r4YJG
#webdev#react#OSS
โ v3.3.0 is out!
It introduces a bunch of bug fixes and small improvements:
๐ชฒ A lot of functions are fixed when working with negative fractional values
๐จ๐ฟ ๐ซ๐ท Czech and French fixes
๐ differenceInSeconds function fix
๐ฝ formatDate function alias
๐ v3.2.0 is out
- Fixed types compatibility with Lodash's flow and fp-ts's pipe.
- Fixed inconsistent behavior of roundToNearestMinutes.
-Added exports of format, lightFormat, and parse internals that enable 3rd-parties to consume those.
https://t.co/HU3YQzpjgQ
๐ date-fns v3 is out!
โข Full TypeScript rewrite
โข No more runtime type checking
โข Minimal size is now 200 bytes!
โข String arguments are back!
โข UTCDate
โข Node.js ESM support
โข No more default exports
โข New flat library structure
โข No more IE
Should date-fns accept strings as arguments? I will abide by the results of this poll.
For context - we removed strings in v2 to avoid bugs caused by engine differences and parsing time zone nuances.
Today's date is written 7/7 in the USA. It's also written 7/7 everywhere else in the world, because that's how dates work.
This pattern will repeat 5 more times this year, and 12 times in 2024 and every subsequent year.
It only happens once per month.