@aws/nx-plugin-mcp 1.0.0-rc.54 → 1.0.0-rc.56

package/bin/aws-nx-mcp.js

@@ -20779,16 +20779,9 @@ var import_lodash_deburr = /* @__PURE__ */ __toESM(require_lodash_deburr(), 1);
 const kebabCase = (str) => {
 	return (0, import_lodash_deburr.default)(str).replace(/[^a-zA-Z0-9]+/g, "-").replace(/([a-z0-9])([A-Z])/g, "$1-$2").toLowerCase().replace(/^-+|-+$/g, "");
 };
-//#endregion
-//#region ../nx-plugin/src/utils/commands.ts
-/**
-* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
-* SPDX-License-Identifier: Apache-2.0
-*/
 /**
-* The nx version the plugin is built against. Commands that download nx
-* (e.g. `nx init`) pin to this version so the workspace's nx matches the
-* plugin's `@nx/*` packages — a mismatch deadlocks `nx sync`.
+* The nx version the plugin is built against, and the single source of truth
+* for every place a workspace's nx is pinned.
 */
 const NX_VERSION = {
 	"@a2a-js/sdk": "0.3.14",
@@ -20817,8 +20810,13 @@ const NX_VERSION = {
 	"@middy/core": "7.7.0",
 	"@nxlv/python": "22.2.2",
 	"@nx-extend/terraform": "10.3.0",
+	nx: "23.1.0",
 	"@nx/devkit": "23.1.0",
+	"@nx/js": "23.1.0",
 	"@nx/react": "23.1.0",
+	"@nx/vite": "23.1.0",
+	"@nx/vitest": "23.1.0",
+	"@nx/workspace": "23.1.0",
 	"create-nx-workspace": "23.1.0",
 	"@swc-node/register": "1.12.1",
 	"@swc/core": "1.15.43",
@@ -20916,7 +20914,13 @@ const NX_VERSION = {
 	vitest: "4.1.10",
 	zod: "4.4.3",
 	ws: "8.21.1"
-}["@nx/devkit"];
+}.nx;
+//#endregion
+//#region ../nx-plugin/src/utils/commands.ts
+/**
+* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+* SPDX-License-Identifier: Apache-2.0
+*/
 const PACKAGE_MANAGER_COMMANDS = {
 	npm: {
 		exec: "npx",

package/docs/guides/nx-migration.mdx

@@ -75,7 +75,7 @@ export default async function migration(
 }
 ```
 
-- **`nextSteps`** — workspace-wide notes surfaced to the user after `nx migrate` runs. Use these to report files you skipped (see the guardrails below) or manual follow-up the migration couldn't perform.
+- **`nextSteps`** — the follow-up actions Nx prints for the user after `nx migrate` runs. Every entry should be something they need to do by hand: reconcile a file you skipped (see the guardrails below), or finish something beyond the migration's reach, like an install to refresh a lock file. They aren't a log of what you changed — when a transform applies cleanly, add nothing, otherwise the entries that do need action get buried.
 - **`agentContext`** (hybrid only) — a summary of what the codemod changed, passed to the paired `prompt` when it runs under Nx's agentic flow so the agent can focus on the user-owned parts.
 
 For some example operations you can perform in your migration (generating files, modifying existing files using GritQL, reading and updating JSON), refer to the <Link path="/guides/nx-generator">Nx Generator guide</Link>.
@@ -86,6 +86,7 @@ Migrations run against workspaces you don't control, so it is recommended to adh
 
 - **Transform source code with GritQL.** Use the <Link path="/guides/nx-generator">GritQL helpers</Link> (`applyGritQL`, `matchGritQL`) to edit source rather than regexes or string replacements. GritQL matches the AST, so one pattern holds across the formatting, whitespace and quoting a user's copy may have drifted into, where text matching quietly misses equivalent code or corrupts the file. Use `updateJson` for JSON and the matching parser for other structured config.
 - **Pattern-match before writing.** If a target file has diverged from the shape your generators produce, skip it and report it via `nextSteps`, or consider a hybrid migration, rather than clobbering the user's changes. `matchGritQL` is a convenient way to make that check.
+- **Report only what's left to do.** `nextSteps` is for work the user has to pick up, not a record of the edits you made — those are already in their `git diff`.
 - **Idempotent.** Re-running the migration must be a no-op. Guard GritQL rewrites that inject code with a `where { ... <: not contains ... }` clause so a second run doesn't append a duplicate.
 - **Format what you write.** Finish with `formatFilesInSubtree(tree)` so the files your migration wrote are formatted correctly.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws/nx-plugin-mcp",
-  "version": "1.0.0-rc.54",
+  "version": "1.0.0-rc.56",
   "repository": {
     "type": "git",
     "url": "https://github.com/awslabs/nx-plugin-for-aws.git",