title: React i18-next - why to use the i18next-http-backend instead of imports?
body: <p>I am introducing <a href="https://react.i18next.com/" rel="nofollow noreferrer">https://react.i18next.com/</a> into my ReactJS application and wondering why it is necessary or useful to actually use the <strong>i18next-http-backend</strong>
  (see <a href="https://react.i18next.com/latest/i18next-instance" rel="nofollow noreferrer">https://react.i18next.com/latest/i18next-instance</a>) ?</p>
  <p>I understand that they put localization files into the public/ folder and files normally cannot be imported from other directories than the src/ folder of a project in ReactJS (create-react-app) by default.</p>
  <p>My question therefor is: What arguments are their against the approach of storing the localization files within the
  <strong>src folder</strong> and normally import them by using:</p>
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-js lang-js prettyprint-override"><code>import en from "localization/en.json";
  import de from "localization/de.json";
  import es from "localization/es.json";</code></pre>
  </div>
  </div>
  </p>
  <p>? I appreciate any answer, also links to articles where infos can be found about this.</p>