-
-
Notifications
You must be signed in to change notification settings - Fork 629
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't transpile to es5 #1948
Comments
we'll evaluate that for the next major |
I only use i18next serverside in a nodejs application so I'm less concerned about package size, but I would also like a way in require() a non-babeled version of i18next. Babel has introduced a lot of es6 polyfils into the package which have a big performance impact, the i18next object spread polyfil is the hottest code path in my whole application, replacing the npm installed package with a non-babled version of the library increaed my requests per second by 10%! |
prepared for next major version |
馃殌 Feature Proposal
We are in 2023, and maybe we can try targeting es6 (especially because this package dropped support for IE in 3 years ago).
This can be easily done by adding
Motivation
I'm using
i18next
in several applications (troughnext-i18next
), and often,i18next
is a single biggest dependency I have at 100kb (non-minified).defaults
ofbrowserlists
targets es6, and this single change drops esm build size down to 81kb. (approx. -20%)Example
Smaller builds, faster loads worldwide.
The text was updated successfully, but these errors were encountered: