[plugin] `CustomParseFormat` parsing problem.
- Dominant language
- JavaScript
- Stars
- 48.7k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Using the `CustomiParseFormat` plugin:

**Expected behavior**
Normal, not `Invalid Date`.
**Information**
- Day.js Version 1.11.8
- OS: Mac
- Browser Edge
- Time zone: [e.g. GMT-07:00 DST (Pacific Daylight Time)]
Contributor guide
Research direction
Start by reproducing the reported CustomParseFormat plugin behavior with Day.js 1.11.8 using the example shown in the issue image. No source file, test, or exact input format is provided, so identify the plugin entry point and add a regression test once the failing case is known; done means the same input no longer produces Invalid Date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100