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

chore!: drop support for Node.js<20 #344

Merged
merged 2 commits into from
Mar 4, 2025
Merged

Conversation

fisker
Copy link
Collaborator

@fisker fisker commented Mar 1, 2025

Update all deps except these already have separate PRs.

@fisker fisker changed the title chore: drop support for Node.js<20 chore!: drop support for Node.js<20 Mar 1, 2025
@keithamus
Copy link
Owner

This needs rebasing now. Should we wait for #336 first? I am ambivalent.

# Conflicts:
#	package-lock.json
@fisker
Copy link
Collaborator Author

fisker commented Mar 1, 2025

IDK, #336 is currently doing more than fixing #294, I think it's too risky. I hope you can post your opinion there.

@fisker
Copy link
Collaborator Author

fisker commented Mar 2, 2025

I just realized that we are currently not sorting exports at all

{ key: 'exports' },
, but somehow I thought #336 is fixing bugs... I guess we don't need to wait for it.

@keithamus keithamus merged commit 8b701c7 into keithamus:main Mar 4, 2025
2 checks passed
Copy link

github-actions bot commented Mar 4, 2025

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@fisker fisker deleted the node20 branch March 4, 2025 13:59
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.

2 participants