dotcore64 / i18next-fetch-backend

Fetch i18next translations with the fetch API

dotcore64/i18next-fetch-backend Issues

Cant get Multiloading to work and translation key depth problem
Updated 5 months ago
No "exports" main defined
Closed 2 years ago4
Remove @babel/parser-eslint
Closed 3 years ago
Error while migrating to Angular 11
Closed 3 years ago8
An in-range update of mocha is breaking the build 🚨
Closed 4 years ago8
An in-range update of rollup is breaking the build 🚨
Closed 4 years ago86
An in-range update of i18next is breaking the build 🚨
Closed 4 years ago1
An in-range update of babel7 is breaking the build 🚨
Closed 4 years ago54
An in-range update of eslint is breaking the build 🚨
Closed 4 years ago1
Version 10 of node.js has been released
Closed 4 years ago
Add Typescript Bindings
Closed 4 years ago1
Typescript
Closed 4 years ago2
I can use the translation of an api with authorization token?
Closed 4 years ago1
Invalid content-type when posting missing keys
Closed 4 years ago2
Doesn't work for server-side rendered apps
Closed 6 years ago10
[Q] How to cache the response in backend storage?
Closed 5 years ago1
Unhandled Promise Error
Closed 5 years ago1
Increase code coverage
Updated 6 years ago
Simplify fetch backend loader
Closed 6 years ago10
Provide a changelog
Closed 6 years ago1
Still requires i18next-xhr-backend
Closed 6 years ago1
Publish on Bower
Closed 7 years ago4
Doesn't work in Internet Explorer 10 or older.
Closed 7 years ago2