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
JS bundles are decorated with a content hash, so the browser fetches new code after a release, instead of reusing cached code. This is since #318. However, the locale files have permanent names (locale-swe.json etc) so the browser will reuse cached locale files. If the new relase has new or changed translation strings, they will not show correctly.
Locale files are referenced in code, not sure if we can get a Webpack-generated content hash in there.
An alternative could be to include the locale files at build time.
I guess we should be able to dynamically import them, just like we do with Rickshaw and some other things, and then Webpack will sort out hashed filenames?
The text was updated successfully, but these errors were encountered:
JS bundles are decorated with a content hash, so the browser fetches new code after a release, instead of reusing cached code. This is since #318. However, the locale files have permanent names (
locale-swe.json
etc) so the browser will reuse cached locale files. If the new relase has new or changed translation strings, they will not show correctly.Locale files are referenced in code, not sure if we can get a Webpack-generated content hash in there.
korp-frontend/app/scripts/data_init.ts
Line 25 in 3bda2d0
An alternative could be to include the locale files at build time.
I guess we should be able to dynamically import them, just like we do with Rickshaw and some other things, and then Webpack will sort out hashed filenames?
The text was updated successfully, but these errors were encountered: