Fix time formatting with some environments

[etrappg]

Fix time formatting issue with some environments

Fix #112
Fix #114

[phstc]

Hi @etrappg

Thanks for submitting this 🎉

Would you mind to add some tests here to cover the formats this change is fixing?

[etrappg]

Unfortunately it's difficult to add test for this case: function which bug is internal (parseTime) and the bug occurs when calling parseDate with a Date object, at line 127 of dateFormat.js, the toTimeString() call result is different with some envs, for example, with date 2019-07-31 15:12:13, I have:

• on Firefox, and Windows 10: Date Wed Jul 31 2019 15:12:13 GMT+0200 (heure d’été d’Europe centrale), no problem,
• on Firefox, and Linux Mint: Date Wed Jul 31 2019 15:11:29 GMT+0200 (GMT+02:00), problem with last : of GMT+02:00 timezone

Maybe you have a solution to make this reproducible with tests and node env?

[phstc]

@etrappg I see. I think we can leave it as is, since the test suite is still passing, and we have a plenty of use cases in there, so it shouldn't be breaking any existing formatting.

Thank you for addressing this problem 🎉

I've just released a new version 1.0.4 with your fix.