chore(repo): update nx to 23.0.0-beta.11

[FrozenPandaz]

Updating Nx from 23.0.0-beta.4 to 23.0.0-beta.11

[nx-cloud-snapshot]

View your CI Pipeline Execution ↗ for commit 78eca78

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e-ci,ty...	✅ Succeeded	2m 34s	View ↗
nx-cloud record -- node tools/scripts/check-pin...	✅ Succeeded	<1s	View ↗
nx-cloud record -- yarn nx sync:check	✅ Succeeded	10s	View ↗
nx-cloud record -- yarn nx run-many -t ktfmtFormat	✅ Succeeded	3m 19s	View ↗
nx run-many -t ktfmtFormat	✅ Succeeded	1m 42s	View ↗
nx-cloud record -- yarn nx format:check --verbose	✅ Succeeded	1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-14 04:21:27 UTC

[graphite-app]

Version mismatch between Jest and its environment packages. jest is updated to 30.3.0 while jest-environment-node remains at 29.7.0 (major version behind). This will likely cause compatibility issues since Jest 30.x expects environment packages to be on version 30.x.

"jest": "30.3.0",
"jest-environment-jsdom": "30.3.0",
"jest-environment-node": "30.3.0",

Both jest-environment-jsdom should also be updated from 30.0.5 to 30.3.0 to match the Jest core version, and jest-environment-node needs to be updated from 29.7.0 to 30.3.0.

Suggested change

	"jest": "30.3.0",
	"jest-environment-jsdom": "30.0.5",
	"jest-environment-node": "29.7.0",
	"jest": "30.3.0",
	"jest-environment-jsdom": "30.3.0",
	"jest-environment-node": "30.3.0",

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[nx-cloud-snapshot]

Important

At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

Nx Cloud is proposing a fix for your failed CI:

We update the parseTargetString helper to fix TypeScript compilation failures caused by the @nx/devkit 23.0.0-beta.11 upgrade, which removed the ./src/executors/parse-target-string subpath export and dropped the top-level src/ directory from the published package. These changes resolve all three failing tasks (nx-mcp:build:production, shared-npm:typecheck, vscode:build:ci) by pointing both the runtime import and the TypeScript type annotation at the correct, still-exported locations.

Tip

✅ We verified this fix by re-running shared-npm:typecheck, nx-mcp:build:production.

diff --git a/libs/shared/npm/src/lib/local-nx-utils/parse-target-string.ts b/libs/shared/npm/src/lib/local-nx-utils/parse-target-string.ts
index 79f3066..26937b3 100644
--- a/libs/shared/npm/src/lib/local-nx-utils/parse-target-string.ts
+++ b/libs/shared/npm/src/lib/local-nx-utils/parse-target-string.ts
@@ -14,10 +14,8 @@ export async function parseTargetString(
   if (!devkitPath) {
     throw 'local @nx/devkit dependency not found';
   }
-  const importPath = join(devkitPath, 'src/executors/parse-target-string');
+  const importPath = join(devkitPath, 'dist/src/executors/parse-target-string');
   const { parseTargetString } =
-    await importWorkspaceDependency<
-      typeof import('@nx/devkit/src/executors/parse-target-string')
-    >(importPath);
+    await importWorkspaceDependency<typeof import('@nx/devkit')>(importPath);
   return parseTargetString(targetString, projectGraph);
 }

  

Or Apply changes locally with:

npx nx-cloud apply-locally otbg-ENCj

Apply fix locally with your editor ↗   View interactive diff ↗

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