Skip to content

Conversation

@FrozenPandaz
Copy link
Contributor

@FrozenPandaz FrozenPandaz commented Nov 25, 2025

Updating Nx from 22.1.0-rc.5 to 22.3.0-beta.1

@nx-cloud
Copy link
Contributor

nx-cloud bot commented Nov 25, 2025

View your CI Pipeline Execution ↗ for commit e02c269

Command Status Duration Result
nx affected --targets=lint,test,build,e2e-ci,ty... ❌ Failed 5m 34s View ↗
nx-cloud record -- yarn nx sync:check ✅ Succeeded 4s View ↗
nx-cloud record -- yarn nx run-many -t ktfmtFormat ✅ Succeeded 2m 49s View ↗
nx run-many -t ktfmtFormat ✅ Succeeded 2m 44s View ↗
nx-cloud record -- yarn nx format:check --verbose ✅ Succeeded 2m 45s View ↗

☁️ Nx Cloud last updated this comment at 2025-12-16 16:39:53 UTC

nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz FrozenPandaz changed the title chore(repo): update nx to 22.2.0-beta.0 chore(repo): update nx to 22.2.0-beta.1 Nov 27, 2025
nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz FrozenPandaz changed the title chore(repo): update nx to 22.2.0-beta.1 chore(repo): update nx to 22.2.0-beta.4 Dec 13, 2025
nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz FrozenPandaz changed the title chore(repo): update nx to 22.2.0-beta.4 chore(repo): update nx to 22.3.0-beta.1 Dec 16, 2025
nx-cloud[bot]

This comment was marked as outdated.

Copy link
Contributor

@nx-cloud nx-cloud bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud is proposing a fix for your failed CI:

These changes fix the TypeScript compilation errors across shared-npm:typecheck, nx-mcp:build:production, and vscode:build:ci by adding the missing 'why' property to the PackageManagerCommands fallback implementation. The Nx upgrade to 22.3.0-beta.2 introduced a new required 'why' property in the PackageManagerCommands interface, and we've added the correct npm command ('npm explain') to satisfy this requirement.

We verified this fix by re-running shared-npm:typecheck.

diff --git a/libs/shared/npm/src/lib/local-nx-utils/package-manager-command.ts b/libs/shared/npm/src/lib/local-nx-utils/package-manager-command.ts
index 9fa14f24..63d1f68d 100644
--- a/libs/shared/npm/src/lib/local-nx-utils/package-manager-command.ts
+++ b/libs/shared/npm/src/lib/local-nx-utils/package-manager-command.ts
@@ -88,6 +88,7 @@ export async function getPackageManagerCommand(
       run: (script: any, args: any) =>
         `npm run ${script}${args ? ' -- ' + args : ''}`,
       list: 'npm ls',
+      why: 'npm explain',
       getRegistryUrl: 'npm config get registry',
       publish: (packageRoot, registry, registryConfigKey, tag) =>
         `npm publish "${packageRoot}" --json --"${registryConfigKey}=${registry}" --tag=${tag}`,

Apply fix via Nx Cloud  Reject fix via Nx Cloud


Or Apply changes locally with:

npx nx-cloud apply-locally jcOP-Mfod

Apply fix locally with your editor ↗   View interactive diff ↗


🎓 Learn more about Self-Healing CI on nx.dev

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.

2 participants