chore(repo): update nx to 22.2.0-beta.1

[FrozenPandaz]

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

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b60e24f

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

---

☁️ Nx Cloud last updated this comment at 2025-11-27 23:58:11 UTC

[nx-cloud]

Nx Cloud is proposing a fix for your failed CI:

These changes fix the TypeScript compilation errors by adding the missing 'why' property to the fallback PackageManagerCommands object. The Nx 22.2.0-beta.1 upgrade introduced this new required property to the PackageManagerCommands interface, and the fallback implementation needed to be updated to include 'npm explain' as the npm equivalent for the 'why' command.

We verified this fix by re-running nx-mcp:build:production.

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}`,

  

Or Apply changes locally with:

npx nx-cloud apply-locally 2uTV-09sv

Apply fix locally with your editor ↗   View interactive diff ↗

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