Thanks! Could you also include a unit test so we can be sure this doesn't revert with some future change? The example code from the original issue should do fine.

Also, Were you able to find any other cases of this besides just the one reported? Thanks.

I think there are lots of cases, but I don't know how to summarise the problem in a more analytical way. This is another one I've found by picking numbers manually:

//moment.js 2.11.2
moment.duration(0.1, 'h').minutes()
//6, as expected
moment.duration(4.1, 'h').minutes()
//5
//?!?

but this PR fixes it

Thanks. We'll merge this in the next release. I suppose we'll have to tackle this one report at a time.

Merged in 544a059