Fixes issue #984 (Couldn't parse 20035000 as a date)

[lmizinski]

Fixes problem described in #984

Date format 20035000 is problematic, because it causes error:

Couldn't parse 20035000 as a date
...
Couldn't parse 20251000 as a date

[coveralls]

Coverage increased (+0.02%) to 90.195% when pulling 06e8ac8 on lmizinski:master into 27cee3f on danvk:master.

[danvk]

See also #939. Please add a test to cover this.

[lmizinski]

Thank you for adding me as contributor. I fixed the problem and merged it to master.

I had hard time running tests on Windows (docs on testing are little bit outdated), but I was able to figure it out using Travis log included in pull request.

I had to change locally part of package.json to

"scripts": {
    "build": "bash ./scripts/build.sh",
    "coverage": "bash ./scripts/generate-coverage.sh",
    "watch": "bash ./scripts/watch.sh",
    "build-tests": "bash ./scripts/build-tests.sh",
    "test": "bash ./scripts/run-tests.sh",
    "tests-ok": "bash ./scripts/check-no-only.sh"
  },

and then commands from Travis started working

npm run build-tests
npm run test

[leeoniya]

@lmizinski

I had hard time running tests on Windows

i made a bunch of changes to get tests passing on windows as part of #948.

feel free to pick up that PR, too 👍