Nx
Enterprise
Nx
Overview
Sign in / Sign up
Open main menu
Nx
GitHub
Select a tab
Overview
Runs
Analytics
Nx
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Filter
Filter exact branch match
Exact
Select status
Succeeded
33059
d5843aa8 fix(react): dynamic module federation should not initialize remoteUrlDefinitions to empty object The remoteUrlDefinitions variable was initialized as an empty object, which caused the check in loadRemoteContainer to always be truthy. This prevented resolveRemoteUrl from being called and resulted in cryptic error messages when loadRemoteModule was called before setRemoteDefinitions. This fix applies the same solution that was implemented for Angular in PR #27927, which resolved the same issue reported in #27793. Changes: - Initialize remoteUrlDefinitions without a value (undefined) - Add nullish coalescing operator in setRemoteDefinition to initialize only when needed
3 days ago
by Coly010
Previous page
Previous
Next
Next page