Hey! Thank you for the report. The docs are indeed outdated. For compactness's sake, 0 values are omitted starting from v3. Is there a specific use case for that?

We would like to format it to a "time left" string like 1h 0m 32s. As in the docs we expected minutes to be 0 rather than undefined / not existent.

So to fix this we do something like this right now:

return `${hours || 0}h ${minutes || 0}m ${seconds || 0}s`

@SimonVillage I see, thank you! Yeah, I guess you'll have to go with that. The types also reflect it if that is of any help. I'll make sure to update the docs. Thanks!

I wonder if we can't add an options parameter with zero: true?

@SimonVillage I don't think it's a bad idea, a PR is welcome. If you decide to make it happen, please also add the NormalizedDuration version of the return type and conditionally return it from the function. Tell me if you need help with generics

export type NormalizedDuration = Required<Duration>

0 values are omitted starting from v3

This seems like a very bad move. Function return values should have a definitive shape. Just got bit by it.