Dayjs: YYYY-MM-DD Format Not Working

[GoPro16]

Describe the bug
When passing in a parse format of YYYY-MM-DD with an invalid date string of 10/12/2014, should result in and invalid date but instead resolves to 08-14-2015

Expected behavior
Should result in date.isValid() === false

Information

• Day.js Version [e.g. v1.8.11]
• OS: [e.g. MacOS]
• Browser [e.g. chrome 73]

CodeSandbox Link

---

IssueHunt Summary

iamkun has been rewarded.

Backers (Total: $50.00)

• issuehunt ($50.00)
  

  Submitted pull Requests

- #517 fix: Add UTC mode with UTC plugin

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
  

  - Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

[xxyuk]

With customParseFormat plugin
dayjs('2014-12-01', 'YYYY-MM-DD').toISOString() returns 2014-12-01T00:00:00.000Z

Looks good.

[GoPro16]

@xxyuk Right sorry, I updated my issue comments. If you check the codesandbox it should be throwing an error when trying to parse the invalid date format but instead parses to a random date.

[iamkun]

will fix soon

[IssueHuntBot]

@issuehunt has funded $50.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[iamkun]

:tada: This issue has been resolved in version 1.8.13 :tada:

The release is available on:

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

Your semantic-release bot :package::rocket:

[issuehunt-app[bot]]

@iamkun has rewarded $45.00 to @iamkun. See it on IssueHunt

• :moneybag: Total deposit: $50.00
• :tada: Repository reward(0%): $0.00
• :wrench: Service fee(10%): $5.00