WilcoSp

this comes from the [date function](https://github.com/formkit/tempo/blob/main/src/date.ts) which converts an undefined value to a new Date object with the current time. for at least the `is*` and `diff*` functions it might...

If it would be implemented I do think it would be best to use typescript's [function overload](https://www.typescriptlang.org/docs/handbook/2/functions.html#function-overloads) feature to provide more jsdoc, but also prevent unexpected behaviour from being created...

hey @justin-schroeder it's not an issue, I was also busy the past month. When I've sometime (most likely on Wednesdays) I'll bring optional date arguments to other functions.

@justin-schroeder all the functions where possible have given been optional date arguments (check top post for which ones have been changed). I've also added `isPast` & `isFuture` as I think...

@SeanLuis & @justin-schroeder maybe best to split the `formatOrParseDuration` function up into multiple functions to allow for better bundle sizes & also allows developers to decide on their own how...

I'm also experiencing this with web components, only attributes & boolean attributes are being rendered in the code block when using a custom render function. but when using attributes it...

I've also ran into this and I've also tested both the [capture option](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#usecapture) and adding an event listener to each component/element. Using the capture option would be the cleanest and...

I've tried to implement it myself once before, but because I use pnpm instead of yarn I hadn't much success to create a commit/pr for it. maybe in the feature...