Do not throw if a progress is less than last value

[timlesallen]

Since you can't guarantee that async stuff will evaluate in order, it's conceivable that event handlers may be evaluated out of order (I've noticed this in a browser after tabbing away and coming back.)

Fixes #8

[revelt]

Algorithm does make sense and that was what came to my mind too. I'm thinking, API-wise, if somebody needs strict, current behaviour, in the future, we could always add a new options' setting, something like opts.strict or opts.noLesserReportedValues? Although it's hard to imagine, after all this program is just for progress reporting, it's not mission-critical... So what if some percentages will move slower at some point...

[sindresorhus]

Can you also document this new behavior in the readme? I think it's good to be explicit about it that p-progress only passes the progress values you supply through. It doesn't enforce it to be higher than the last.

Same text in https://github.com/sindresorhus/p-progress/blob/master/index.d.ts too.

[timlesallen]

Can you also document this new behavior in the readme? I think it's good to be explicit about it that p-progress only passes the progress values you supply through. It doesn't enforce it to be higher than the last.

Same text in https://github.com/sindresorhus/p-progress/blob/master/index.d.ts too.

Will do.

[timlesallen]

@sindresorhus Back to you.

[sindresorhus]

Thanks :)