You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrading from v20.6.1 to v21.0.0 causes a custom backend to stop working. I reviewed the migration guide and did not see any changes that would imply a custom backend stops working. Roughly, this is the contents of my custom backend
classBackend{constructor(services,backendOptions={},i18nextOptions={}){this.init(services,backendOptions,i18nextOptions);}init(services,backendOptions,i18nextOptions){// init code}// Writes a given translation to filewrite(writeQueue){// code}// Reads a given translation filerequestFileRead(filename,callback){// code}// Reads a given translation fileread(language,namespace,callback){// code}// Not implementing at this timereadMulti(languages,namespaces,callback){throw"Not implemented exception.";}// Writes a missing translation to filecreate(languages,namespace,key,fallbackValue,callback){// code}}Backend.type="backend";exportdefaultBackend;
To Reproduce
git clone https://github.com/reZach/secure-electron-template.git
cd secure-electron-template
// change i18next dependency in package.json from ^20.6.1 to ^21.0.0
npm i
npm run dev
Expected behavior
I expect the following error will not be thrown; "Uncaught TypeError: Cannot read property 'use' of undefined"
Your Environment
runtime version: node v16.13.0, electron v13.6.2
i18next version: 21.0.0 (20.6.1 does not have this issue)
os: Windows
The text was updated successfully, but these errors were encountered:
馃悰 Bug Report
Upgrading from v20.6.1 to v21.0.0 causes a custom backend to stop working. I reviewed the migration guide and did not see any changes that would imply a custom backend stops working. Roughly, this is the contents of my custom backend
To Reproduce
Expected behavior
I expect the following error will not be thrown; "Uncaught TypeError: Cannot read property 'use' of undefined"
Your Environment
The text was updated successfully, but these errors were encountered: