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
Im using i18next with react-18next, and loading my language files over http. Currently my tooling just drops the translation json files into the public directory for easy access. I'm thinking I now need to hash these, similar to the job and css file in the build. Is there a recommended way to about doing this?
My thought is to use a hashing npm package, and export the file names into my code through a module that checks the node environment to return the proper name.
Any thoughts on the best way do this in CRA?
The text was updated successfully, but these errors were encountered:
I don't have any suggested approach, sorry. Personally I’m concerned about react-i18next since its implementation looks very inefficient. I’d probably suggest trying #1227 (comment) instead.
Is this a bug report?
No
Im using i18next with react-18next, and loading my language files over http. Currently my tooling just drops the translation json files into the public directory for easy access. I'm thinking I now need to hash these, similar to the job and css file in the build. Is there a recommended way to about doing this?
My thought is to use a hashing npm package, and export the file names into my code through a module that checks the node environment to return the proper name.
Any thoughts on the best way do this in CRA?
The text was updated successfully, but these errors were encountered: