no second format compatibility problem.

[AxeMea]

The Date Object has some unexpected behaviors on iOS device when the format of input value like YYYY-MM-DD HH:mm ( no second ).

// iOS device
// NaN
new Date('2018-12-12 11:12')

// other device
// right
new Date('2018-12-12 11:12')

The REGEX_PARSE regular expression in dayjs can't match the YYYY-MM-DD HH:mm format as input value. then return new Date(string) directly. so it has the same problem too.

I guess that developers usually use the kind of format data in work.

The unexpected behavior have many potential risks when the data format is unsure or developers don't check it carefully.

I test 'moment.js' too, It behave correctly.

so, it's better if fix it.

thx.

[codecov-io]

Codecov Report

Merging #411 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #411   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          56     56           
  Lines         491    491           
  Branches       76     76           
=====================================
  Hits          491    491

Impacted Files	Coverage Δ
src/index.js	100% <ø> (ø)	⬆️
src/constant.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73eb122...e450e17. Read the comment docs.

[ghost]

should we also check YYYY-MM-DD HH:mm:ss?

[AxeMea]

#260

[iamkun]

🎉 This PR is included in version 1.8.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀