-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
Support es modules #1998
Support es modules #1998
Conversation
Socket Security Pull Request Report👍 No new dependency issues detected in pull request Pull request report summary
Bot CommandsTo ignore an alert, reply with a comment starting with Powered by socket.dev |
# Conflicts: # CHANGELOG.md
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Rework publishing iteration 1.
Why ?
It paves the way to:
Version
Minor version. Should not break anything.
Risks
Dual packaging is always tricky. There's risks to add the exports field. Out of my mind (not exhaustive):
Next iterations
I'll detail soon. But I see a lot of potential for either size-reduction, either normalization. Other packages i18next, react-i18next will have to be updated too to bring full potential.
Size history
Before:
After:
No regressions