Use lazy loading import for i18n files

[jweisman]

Intended to resolve the following issues:

• 404 errors for non-existent languages/translations from TranslateHttpLoader
• JSON files are cached after new build and translations are not available

Solution based on ngx-translate/http-loader#25 (comment)

[jweisman]

@exlbashirn - can you check out this solution to the caching issue (and the 404s)? I'd be interested if there is a better option to the relative load of the files (i.e. ../../.ng/...). Thanks!

[exlbashirn]

Hi @jweisman

I'm not sure about the dependency importing on behalf the dependent.

There is not a lot of room here to do it differently with dynamic imports since webpack needs the hint, so if you want to do it this way and have it be transparent, then what you did is probably it, but this is making a lot of assumptions... though I suppose in our case they're likely to be true most of the time.

The alternative with the same approach is to instead have the import outside in the app.

Also, if you're doing it this way, it would not make sense to have the translations in the assets folder, as they would no longer be needed as static files.

[exlbashirn]

Is the export really needed here?

[jweisman]

Thanks. I moved the files out of assets and into /src/i18n. And you're right- no need for the export here.

I looked for alternatives to the import in the dependency, but I couldn't find anything better. The assumptions are definitely more brittle than I would like. But it may be the best option at this point.