Export `dayjs.Dayjs` in source to keep the same as type definition
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 48.7k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Currently there is a `Dayjs` class definition in declaration file locates on `dayjs.Dayjs`. But in source there is no a `Dayjs` property of `dayjs`. It's confusing that TS tells developers they can access `dayjs.Dayjs` but actually they can't.
**Expected behavior**
Also export `Dayjs` in source.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the source export entry point and comparing it with the declaration file that exposes dayjs.Dayjs. Confirm the existing package checks for exports, then verify that the runtime dayjs.Dayjs property is available and matches the type definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100