Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: migrate to ESM #4

Closed
wants to merge 1 commit into from

Conversation

Gopikrishna19
Copy link

@Gopikrishna19 Gopikrishna19 commented Jul 15, 2022

BREAKING CHANGE: This package is now pure ESM. Please use the supporting Node.js version to use this package. Or keep using v2.x until you are ready to switch

closes #3

@haversnail please review and merge. Thank you!

BREAKING CHANGE: This package is now pure ESM. Please use supporting Node.js version to use this package. Or keep using v2.x until you are ready to switch

closes haversnail#3
@Gopikrishna19
Copy link
Author

Gopikrishna19 commented Jul 19, 2022

@haversnail hey, can I get a review/merge on this, please? I have an ESM project and want to use this date picker. I couldn't
find a better library than yours. I am using a locally modified copy of yours, but I would rather use your package to reduce code redundancy. Please let me know if something has to be changed or anything, I will be happy to get it done :)

@haversnail
Copy link
Owner

@Gopikrishna19 thanks for picking up this work! Absolutely, let me take a look and see if we can get this merged as soon as possible.

Copy link
Owner

@haversnail haversnail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just need to bump the node version in the GitHub action workflow, but other than that looks good! Thanks again for tackling this. 🙏 Let me know if you would rather me jump in and fix, otherwise I'll keep an eye out for the change.

NODE_VERSION: "12"
NODE_VERSION: "12.20.0"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that semantic-release was bumped to v19 (and the git plugin to v10)... it looks like as of v18, the minimum required version of node is v14.17 (release notes here). Though v12 should be fine for consumers of the package, we'll probably need to make sure that the GitHub action runners are on the latest minor version of 14 so that Semantic Release works correctly:

  NODE_VERSION: "14"

Comment on lines -23 to +24
"node": ">=10"
"node": "^12.20.0 || ^14.13.1 || >=16.0.0"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, any reason for 12.20.0 or 14.13.1 specifically?

@haversnail
Copy link
Owner

@Gopikrishna19 is this still something you're interested in working on? No worries if not, just let me know and I can see about making the changes.

@haversnail haversnail self-assigned this Sep 9, 2022
@ABHammad
Copy link

ABHammad commented Oct 3, 2022

Hello,
I am waiting this PR to be release awhile ago :)
If there is something I can help with. looking forward to use this change ASAP

@github-actions
Copy link

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@haversnail
Copy link
Owner

haversnail commented Oct 12, 2022

@ABHammad thanks for your patience (and for the nudge)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support ES Modules
3 participants