Skip to content

Conversation

@yassinesos
Copy link

Problem

Two issues with translateFederationArtefacts:

  1. Windows paths with spaces break the localize-translate command
  2. Lazy-loaded chunks containing $localize markers are not translated (only federation artifacts in shared/exposes were processed)

Solution

  • Quote all paths in the command for Windows compatibility
  • Use *.js pattern to translate ALL JS files, including lazy chunks

Fixes #1055

…ows paths

## Problem
Two issues with `translateFederationArtefacts`:
1. **Windows paths with spaces** break the `localize-translate` command
2. **Lazy-loaded chunks** containing `$localize` markers are not translated
   (only federation artifacts in `shared`/`exposes` were processed)

## Solution
- Quote all paths in the command for Windows compatibility
- Use `*.js` pattern to translate ALL JS files, including lazy chunks

Fixes angular-architects#1055
@Aukevanoost Aukevanoost merged commit 372e88b into angular-architects:main Feb 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

localize-translate misses non-federation code-split chunks

2 participants