Closed fynncfchen closed 4 years ago
Hi Team, thank you for making this package. We are using it in our project. Can I just clarify why you are deprecating i18next-xhr-backend
in favour for i18next-http-backend
. We've done a little digging but haven't found why this is happening.
Is it just a name change?
Thank you for taking the time to respond to this.
i18next-xhr-backend was just using the XMLHttpRequest... so this was more or less a browser only module... i18next-http-backend is using the fetch api and if not there as fallback the XMLHttpRequest. And the way it is built, it's usable also in Node.js and Deno environment.
i18next-xhr-backend was just using the XMLHttpRequest... so this was more or less a browser only module... i18next-http-backend is using the fetch api and if not there as fallback the XMLHttpRequest. And the way it is built, it's usable also in Node.js and Deno environment.
Nice update!, could you put this clarification at the top of the Readme's for both so it's clear for the next newbie?
đ Bug Report
I found this package should not marked as deprecated because the package
i18next-http-backend
doesn't work properly with Parcel.To Reproduce
Reported to
i18next-http-backend
already: https://github.com/i18next/i18next-http-backend/issues/15i18next-xhr-backend
for the first time oni18n.js
i18next-http-backend
module
field onpackage.json
then include some non-transpiled codesi18n.js
i18nextHttpBackend.js
explicitlyExpected behavior
Should not marked as deprecated package until the new replacement
i18next-http-backend
can work properly on Parcel.Your Environment
package.json
.babelrc
.browserslistrc