Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
33070
7b2e1b84 fix(release): ensure multilines in breaking changes are rendered by changelog renderer
19 hours ago by Coly010
Failed
33056
43bf2269 fix(react): change afterEach to afterAll in ts-solution-mf e2e test The test was failing with "spawnSync /bin/sh ENOENT" errors because afterEach was cleaning up the test environment after the first test, causing subsequent tests to fail when they tried to run CLI commands. Since each test uses uniq() to generate unique project names, all tests can safely run in the same workspace. The cleanup should only happen once after all tests complete. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
20 hours ago by Coly010
Failed
33056
3fd8acd9 fix(react): ensure host and remote use project name in ts soln generation
21 hours ago by Coly010
Succeeded
master
aac83097 fix(react): dynamic module federation should not initialize remoteUrlDefinitions to empty object (#33059) ## Current Behavior The `remoteUrlDefinitions` variable in `packages/react/mf/dynamic-federation.ts` is initialized as an empty object (`{}`), which causes: 1. The `resolveRemoteUrl` callback is never called because `remoteUrlDefinitions` is always truthy 2. When `loadRemoteModule` is called before `setRemoteDefinitions`, users get a cryptic error "Cannot read properties of undefined (reading 'endsWith')" instead of the helpful error message ## Expected Behavior - `resolveRemoteUrl` should be called when provided and `remoteUrlDefinitions` hasn't been set - The helpful error message should be shown when `loadRemoteModule` is called before setup ## Changes Made Applied the same fix from PR #27927 (for Angular) to the React implementation: - Changed `remoteUrlDefinitions` initialization to be `undefined` by default - Added nullish coalescing operator (`??=`) in `setRemoteDefinition` to initialize only when needed ## Related Issue(s) Fixes #33055 This follows the same pattern as PR #27927 which fixed #27793 and #27842 for Angular.
23 hours ago by Coly010
Failed
33056
f1a9f868 chore(react): ensure packageJson is also checked for nx targets
1 day ago by Coly010
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
2 days ago by Coly010
Failed
33056
5273ea20 feat(module-federation): support TS Soln and Package Manager workspaces paradigms
2 days ago by Coly010
Failed
33056
fc754688 feat(module-federation): support TS Soln and Package Manager workspaces paradigms
2 days ago by Coly010