Maurice c3c21fb0b4 fix(client): five loads that catch their own error recover from a deploy too ...

The PDF export on desktop and phone, the language switch, the holiday
regions and the PDF's map image load a chunk on demand and catch the
failure themselves. After a deploy the old page asks for chunk names the
new build no longer has, so they showed their own error on every retry
(or, for the language, silently stayed in the old one) instead of
reloading onto the new build the way an uncaught chunk error does.
importChunk reloads once for a missing chunk and still hands the caller
its error.

2026-10-07 17:05:36 +02:00

..

index.ts

v3.1.4 (#1371)

2026-07-01 18:57:16 +02:00

supportedLanguages.ts

Release 3.1.0 (#1185)

2026-06-16 22:22:45 +02:00

TransHtml.tsx

Release 3.1.0 (#1185)

2026-06-16 22:22:45 +02:00

translateApiError.test.ts

v3.1.4 (#1371)

2026-07-01 18:57:16 +02:00

translateApiError.ts

v3.1.4 (#1371)

2026-07-01 18:57:16 +02:00

TranslationContext.tsx

fix(client): five loads that catch their own error recover from a deploy too

2026-10-07 17:05:36 +02:00