🎁 2.0 Milestones【Breaking Change】 · iamkun/dayjs#1281

(38 comments) (17 reactions) (0 assignees)JavaScript (48,643 stars) (2,426 forks)batch import

Breaking Changediscussionhelp wanted🚨 High Priority

Description

We want to make some changes to make Day.js modern and in a standard JS way.

And this would be a breaking change because of these changes below:

Update types/index.d.ts to export default dayjs;

Update package.json "module" to "esm/index", (won't introduce in "dayjs", see https://github.com/iamkun/dayjs/issues/1281#issuecomment-754381268)

Publish a new NPM package, maybe "dayjs-esm" to ship an ESM module with package.json module entry pointed to. ref https://github.com/iamkun/dayjs/issues/1242#issuecomment-734321931

Tech stack: javascripttypescript
Domain: developer experiencetoolingbuild system
Issue type: feature
Difficulty: 5
Estimated time: over 1 week
Activity status: stale
Clarity: clear
Prerequisites: TypeScript basicsES module systemDay.js internals
Newbie friendliness: 15
Research direction: Investigate the two proposed changes: updating types/index.d.ts to export default dayjs and creating a separate ESM package (dayjs esm). Look into related discussions in issues #1242 and #1281 comments, and examine the current package.json and type definitions. Consider the impact on existing users and how to maintain backward compatibility where possible.