Conversions from milliseconds are rounded

[gmattie]

ms("2.5 hrs") // 9000000
ms("9000000") // 3h
ms("9000000", { long: true ) // 3 hours

The above code returns "3h" or "3 hours" when a total of 2.5 hrs in milliseconds is parsed.

If there are technical limitations to returning accurate string representations, it would be ideal to provide an example and explanation in the repository readme.md.

[ianmcderp]

This issue would be fixed by merging the CR from #125.

[david-gonzalez-pnw]

Bump on this!! This is a pretty decent bug. It caused us to loose a couple of hours troubleshooting our custom CI system where we couldn't figure out why calculated timeouts weren't being respected (things were timing out earlier).

> ms('1h')
3600000
> ms('73m')
4380000
> ms(4380000)
'1h'

[kud]

Yeah everything is rounded.