@aws/nx-plugin-mcp 1.0.0-rc.46 → 1.0.0-rc.48

package/bin/aws-nx-mcp.js

@@ -20091,7 +20091,7 @@ var generators$1 = {
 	"ts#sync": {
 		"factory": "./src/ts/sync/generator",
 		"schema": "./src/ts/sync/schema.json",
-		"description": "TypeScript path alias sync generator",
+		"description": "TypeScript path alias and local workspace dependency sync generator",
 		"metric": "g29",
 		"hidden": true
 	},
@@ -21303,7 +21303,11 @@ const NX_VERSION = {
 	"@a2a-js/sdk": "0.3.14",
 	"@aws/aws-distro-opentelemetry-node-autoinstrumentation": "0.12.0",
 	"@opentelemetry/propagator-jaeger": "2.9.0",
+	minimatch: "10.2.5",
 	"@aws-sdk/client-dynamodb": "3.1090.0",
+	"@aws-sdk/client-api-gateway": "3.1090.0",
+	"@aws-sdk/client-iam": "3.1090.0",
+	"@aws-sdk/client-bedrock-agentcore": "3.1090.0",
 	"@aws-sdk/client-bedrock-runtime": "3.1090.0",
 	"@aws-sdk/client-s3": "3.1090.0",
 	"@aws-sdk/client-sts": "3.1090.0",
@@ -21457,9 +21461,22 @@ const buildPackageManagerShortCommand = (pm, command) => {
 	return `${PACKAGE_MANAGER_COMMANDS[pm]?.run ?? pm} ${command}`;
 };
 /**
-* Build an install command for a given package manager
+* Build an install command. With `project`, targets that project's manifest
+* (pnpm `--filter` by unscoped name, npm/bun by `projectDir` defaulting to
+* `packages/<name>`, yarn by fully-qualified name); otherwise the root.
 */
-const buildInstallCommand = (pm, pkg, dev) => {
+const buildInstallCommand = (pm, pkg, dev, project, projectDir) => {
+	if (project) {
+		const shortName = project.split("/").pop();
+		const dir = projectDir ?? `packages/${shortName}`;
+		switch (pm) {
+			case "pnpm": return `pnpm add ${dev ? "-D " : ""}${pkg} --filter ${shortName}`;
+			case "yarn": return `yarn workspace ${project} add ${dev ? "-D " : ""}${pkg}`;
+			case "npm": return `npm install --legacy-peer-deps ${dev ? "-D " : ""}${pkg} -w ${dir}`;
+			case "bun": return `bun add ${dev ? "-D " : ""}${pkg} --cwd ${dir}`;
+			default: return `${pm} install ${dev ? "-D " : ""}${pkg}`;
+		}
+	}
 	switch (pm) {
 		case "pnpm": return `pnpm add ${dev ? "-D" : "-"}w ${pkg}`;
 		case "yarn": return `yarn add ${dev ? "-D " : ""}${pkg}`;
@@ -21492,14 +21509,15 @@ const buildNxInitCommand = (pm) => {
 * The package manager is auto-detected by @aws/create-nx-workspace from the
 * invoking command, so --pm is not needed.
 */
-const buildCreateNxWorkspaceCommand = (pm, workspace, iac, tag, module) => {
+const buildCreateNxWorkspaceCommand = (pm, workspace, iac, tag, module, extraArgs) => {
 	return [
 		PACKAGE_MANAGER_COMMANDS[pm]?.create ?? `${pm} create`,
 		tag ? `@aws/nx-workspace@${tag}` : "@aws/nx-workspace",
 		...pm === "npm" ? ["--"] : [],
 		workspace,
 		...iac ? [`--iac=${iac}`] : [],
-		...module ? [`--module=${module}`] : []
+		...module ? [`--module=${module}`] : [],
+		...extraArgs ? [extraArgs] : []
 	].join(" ");
 };
 //#endregion
@@ -28570,7 +28588,7 @@ var init_micromark_factory_space = __esmMin((() => {
 	init_micromark_util_character();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/initialize/content.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/initialize/content.js
 /**
 * @this {TokenizeContext}
 *   Context.
@@ -28632,7 +28650,7 @@ var init_content$1 = __esmMin((() => {
 	content$1 = { tokenize: initializeContent };
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/initialize/document.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/initialize/document.js
 /**
 * @this {TokenizeContext}
 *   Self.
@@ -34320,7 +34338,7 @@ var init_micromark_core_commonmark = __esmMin((() => {
 	init_thematic_break$1();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/initialize/flow.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/initialize/flow.js
 /**
 * @this {TokenizeContext}
 *   Self.
@@ -34363,7 +34381,7 @@ var init_flow = __esmMin((() => {
 	flow$1 = { tokenize: initializeFlow };
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/initialize/text.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/initialize/text.js
 /**
 * @param {'string' | 'text'} field
 *   Field.
@@ -34533,7 +34551,7 @@ var init_text$1 = __esmMin((() => {
 	text$2 = initializeFactory("text");
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/constructs.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/constructs.js
 var constructs_exports = /* @__PURE__ */ __exportAll({
 	attentionMarkers: () => attentionMarkers,
 	contentInitial: () => contentInitial,
@@ -34604,7 +34622,7 @@ var init_constructs = __esmMin((() => {
 	disable = { null: [] };
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/create-tokenizer.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/create-tokenizer.js
 /**
 * Create a tokenizer.
 * Tokenizers deal with one type of data (e.g., containers, flow, text).
@@ -35041,7 +35059,7 @@ var init_create_tokenizer = __esmMin((() => {
 	init_micromark_util_resolve_all();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/parse.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/parse.js
 /**
 * @param {ParseOptions | null | undefined} [options]
 *   Configuration (optional).
@@ -35085,7 +35103,7 @@ var init_parse = __esmMin((() => {
 	init_create_tokenizer();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/postprocess.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/postprocess.js
 /**
 * @param {Array<Event>} events
 *   Events.
@@ -35100,7 +35118,7 @@ var init_postprocess = __esmMin((() => {
 	init_micromark_util_subtokenize();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/lib/preprocess.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/lib/preprocess.js
 /**
 * @returns {Preprocessor}
 *   Preprocess a value.
@@ -35189,7 +35207,7 @@ var init_preprocess = __esmMin((() => {
 	search = /[\0\t\n\r]/g;
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@10.2.2/node_modules/micromark/index.js
+//#region ../../node_modules/.pnpm/micromark@4.0.2_supports-color@7.2.0/node_modules/micromark/index.js
 var init_micromark = __esmMin((() => {
 	init_decode_named_character_reference();
 	init_micromark_util_combine_extensions();
@@ -35241,7 +35259,7 @@ var init_micromark_util_decode_string = __esmMin((() => {
 	characterEscapeOrReference = /\\([!-/:-@[-`{-~])|&(#(?:\d{1,7}|x[\da-f]{1,6})|[\da-z]{1,31});/gi;
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-from-markdown@2.0.2_supports-color@10.2.2/node_modules/mdast-util-from-markdown/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-from-markdown@2.0.2_supports-color@7.2.0/node_modules/mdast-util-from-markdown/lib/index.js
 /**
 * Turn markdown into a syntax tree.
 *
@@ -36177,12 +36195,12 @@ var init_lib$20 = __esmMin((() => {
 	own$4 = {}.hasOwnProperty;
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-from-markdown@2.0.2_supports-color@10.2.2/node_modules/mdast-util-from-markdown/index.js
+//#region ../../node_modules/.pnpm/mdast-util-from-markdown@2.0.2_supports-color@7.2.0/node_modules/mdast-util-from-markdown/index.js
 var init_mdast_util_from_markdown = __esmMin((() => {
 	init_lib$20();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-parse@11.0.0_supports-color@10.2.2/node_modules/remark-parse/lib/index.js
+//#region ../../node_modules/.pnpm/remark-parse@11.0.0_supports-color@7.2.0/node_modules/remark-parse/lib/index.js
 /**
 * Aadd support for parsing from markdown.
 *
@@ -36211,13 +36229,13 @@ var init_lib$19 = __esmMin((() => {
 	init_mdast_util_from_markdown();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-parse@11.0.0_supports-color@10.2.2/node_modules/remark-parse/index.js
+//#region ../../node_modules/.pnpm/remark-parse@11.0.0_supports-color@7.2.0/node_modules/remark-parse/index.js
 var remark_parse_exports = /* @__PURE__ */ __exportAll({ default: () => remarkParse });
 var init_remark_parse = __esmMin((() => {
 	init_lib$19();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx-expression@2.0.1_supports-color@10.2.2/node_modules/mdast-util-mdx-expression/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx-expression@2.0.1_supports-color@7.2.0/node_modules/mdast-util-mdx-expression/lib/index.js
 /**
 * Create an extension for `mdast-util-from-markdown` to enable MDX expressions
 * in markdown.
@@ -36328,7 +36346,7 @@ var init_lib$18 = __esmMin((() => {
 	init_default();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx-expression@2.0.1_supports-color@10.2.2/node_modules/mdast-util-mdx-expression/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx-expression@2.0.1_supports-color@7.2.0/node_modules/mdast-util-mdx-expression/index.js
 var init_mdast_util_mdx_expression = __esmMin((() => {
 	init_lib$18();
 }));
@@ -36899,7 +36917,7 @@ var init_stringify_entities = __esmMin((() => {
 	init_lib$16();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx-jsx@3.2.0_supports-color@10.2.2/node_modules/mdast-util-mdx-jsx/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx-jsx@3.2.0_supports-color@7.2.0/node_modules/mdast-util-mdx-jsx/lib/index.js
 /**
 * Create an extension for `mdast-util-from-markdown` to enable MDX JSX.
 *
@@ -37422,12 +37440,12 @@ var init_lib$15 = __esmMin((() => {
 	indent = "  ";
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx-jsx@3.2.0_supports-color@10.2.2/node_modules/mdast-util-mdx-jsx/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx-jsx@3.2.0_supports-color@7.2.0/node_modules/mdast-util-mdx-jsx/index.js
 var init_mdast_util_mdx_jsx = __esmMin((() => {
 	init_lib$15();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdxjs-esm@2.0.1_supports-color@10.2.2/node_modules/mdast-util-mdxjs-esm/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdxjs-esm@2.0.1_supports-color@7.2.0/node_modules/mdast-util-mdxjs-esm/lib/index.js
 /**
 * Create an extension for `mdast-util-from-markdown` to enable MDX.js ESM in
 * markdown.
@@ -37500,12 +37518,12 @@ var init_lib$14 = __esmMin((() => {
 	init_default();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdxjs-esm@2.0.1_supports-color@10.2.2/node_modules/mdast-util-mdxjs-esm/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdxjs-esm@2.0.1_supports-color@7.2.0/node_modules/mdast-util-mdxjs-esm/index.js
 var init_mdast_util_mdxjs_esm = __esmMin((() => {
 	init_lib$14();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx@3.0.0_supports-color@10.2.2/node_modules/mdast-util-mdx/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx@3.0.0_supports-color@7.2.0/node_modules/mdast-util-mdx/lib/index.js
 /**
 * Create an extension for `mdast-util-from-markdown` to enable MDX (ESM, JSX,
 * expressions).
@@ -37547,7 +37565,7 @@ var init_lib$13 = __esmMin((() => {
 	init_mdast_util_mdxjs_esm();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-mdx@3.0.0_supports-color@10.2.2/node_modules/mdast-util-mdx/index.js
+//#region ../../node_modules/.pnpm/mdast-util-mdx@3.0.0_supports-color@7.2.0/node_modules/mdast-util-mdx/index.js
 var init_mdast_util_mdx = __esmMin((() => {
 	init_lib$13();
 }));
@@ -50427,7 +50445,7 @@ var init_micromark_extension_mdxjs = __esmMin((() => {
 	init_micromark_util_combine_extensions();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-mdx@3.1.1_supports-color@10.2.2/node_modules/remark-mdx/lib/index.js
+//#region ../../node_modules/.pnpm/remark-mdx@3.1.1_supports-color@7.2.0/node_modules/remark-mdx/lib/index.js
 /**
 * Add support for MDX (JSX: `<Video id={123} />`, export/imports: `export {x}
 * from 'y'`; and expressions: `{1 + 1}`).
@@ -50457,7 +50475,7 @@ var init_lib$8 = __esmMin((() => {
 	emptyOptions$1 = {};
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-mdx@3.1.1_supports-color@10.2.2/node_modules/remark-mdx/index.js
+//#region ../../node_modules/.pnpm/remark-mdx@3.1.1_supports-color@7.2.0/node_modules/remark-mdx/index.js
 var remark_mdx_exports = /* @__PURE__ */ __exportAll({ default: () => remarkMdx });
 var init_remark_mdx = __esmMin((() => {
 	init_lib$8();
@@ -53412,7 +53430,7 @@ function escapeStringRegexp(string) {
 }
 var init_escape_string_regexp = __esmMin((() => {}));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-frontmatter@2.0.1_supports-color@10.2.2/node_modules/mdast-util-frontmatter/lib/index.js
+//#region ../../node_modules/.pnpm/mdast-util-frontmatter@2.0.1_supports-color@7.2.0/node_modules/mdast-util-frontmatter/lib/index.js
 /**
 * Create an extension for `mdast-util-from-markdown`.
 *
@@ -53563,12 +53581,12 @@ var init_lib$1 = __esmMin((() => {
 	init_escape_string_regexp();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/mdast-util-frontmatter@2.0.1_supports-color@10.2.2/node_modules/mdast-util-frontmatter/index.js
+//#region ../../node_modules/.pnpm/mdast-util-frontmatter@2.0.1_supports-color@7.2.0/node_modules/mdast-util-frontmatter/index.js
 var init_mdast_util_frontmatter = __esmMin((() => {
 	init_lib$1();
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-frontmatter@5.0.0_supports-color@10.2.2/node_modules/remark-frontmatter/lib/index.js
+//#region ../../node_modules/.pnpm/remark-frontmatter@5.0.0_supports-color@7.2.0/node_modules/remark-frontmatter/lib/index.js
 /**
 * Add support for frontmatter.
 *
@@ -53599,7 +53617,7 @@ var init_lib = __esmMin((() => {
 	emptyOptions = "yaml";
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/remark-frontmatter@5.0.0_supports-color@10.2.2/node_modules/remark-frontmatter/index.js
+//#region ../../node_modules/.pnpm/remark-frontmatter@5.0.0_supports-color@7.2.0/node_modules/remark-frontmatter/index.js
 var remark_frontmatter_exports = /* @__PURE__ */ __exportAll({ default: () => remarkFrontmatter });
 var init_remark_frontmatter = __esmMin((() => {
 	init_lib();
@@ -54451,12 +54469,11 @@ ${PACKAGE_MANAGERS.map((pm) => buildNxCommand("<options>", pm)).join(" - \n")}
 
 ## General Instructions
 
-- Workspaces contain a single \`package.json\` file at the root which defines the dependencies for all projects. Therefore when installing dependencies, you must add these to the root workspace using the appropriate command for your package manager:
-  - pnpm add -w -D <package>
-  - yarn add -D <package>
-  - npm install --legacy-peer-deps -D <package>
-  - bun add -D <package>
-  - (Omit -D for production dependencies)
+- Each project declares the third-party runtime dependencies its source imports in its own \`package.json\`; shared build/test tooling (test runners, bundlers, etc.) is declared in the root \`package.json\` \`devDependencies\`. Versions follow a single version policy, recorded in the package manager's dependency catalog where supported (referenced as \`catalog:\`). Install with the appropriate command for your package manager:
+  - Add a project runtime dependency: \`pnpm add <package> --filter <project>\` / \`yarn workspace <project> add <package>\` / \`npm install <package> -w <project>\` / \`bun add <package> --cwd <project-directory>\`
+  - Add a shared dev tool at the root: \`pnpm add -Dw <package>\` / \`yarn add -D <package>\` / \`npm install --legacy-peer-deps -D <package>\` / \`bun install -D <package>\`
+- The \`noUndeclaredDependencies\` lint rule enforces that a project's source only imports packages declared in its own \`package.json\`
+- Projects in the same workspace can import one another directly by package name (eg \`@workspace-name/project-name\`) without declaring a dependency in \`package.json\` — TypeScript path aliases in \`tsconfig.base.json\` resolve these imports
 - When specifying project names as arguments to generators, prefer the _fully qualified_ project name, for example \`@workspace-name/project-name\`. Check the \`project.json\` file for the specific package to find its fully qualified name
 - When no generator exists for a specific framework required, use the base \`ts#project\` and \`py#project\` generators and build on top.
 - Leave the \`--infra\` option at its default value unless the user has explicitly instructed otherwise. Generators choose a sensible default type of infrastructure to deploy the project with, so only override \`--infra\` when the user has specified a particular requirement.

package/docs/get_started/existing-project.mdx

@@ -124,9 +124,9 @@ It creates or updates the following files:
 - tsconfig.json a root TypeScript config referencing your workspace's projects, which Nx's TypeScript sync keeps up to date
 - tsconfig.base.json the shared compiler options the plugin's TypeScript projects extend (see below for what it carries)
 - pnpm-workspace.yaml (pnpm only) allow-lists the build scripts the plugin's dependencies need (`@swc/core`, `esbuild`, `nx`, `sharp`)
-- package.json convenience scripts for common tasks, plus the `nx`, `@nx/js`, `@nx/workspace`, `typescript` and Biome dev dependencies
+- package.json convenience scripts for common tasks, plus the `@aws/nx-plugin`, `@aws/nx-plugin-mcp`, `nx`, `@nx/js`, `@nx/workspace`, `typescript` and Biome dev dependencies
 - biome.json default Biome formatter and linter configuration
-- .mcp.json configures the MCP server for supported coding agents unless disabled (also .cursor/, .kiro/, .gemini/, .vscode/ and .codex/ equivalents)
+- .mcp.json configures the MCP server for supported coding agents unless disabled (also .cursor/, .kiro/, .gemini/, .vscode/ and .codex/ equivalents). It runs the workspace's own `@aws/nx-plugin-mcp`, so the server always matches the version installed in your workspace
 </FileTree>
 
 The <Link path="get_started/building-with-ai">MCP server</Link> configuration can be disabled with `--mcp=false`.
@@ -143,6 +143,10 @@ The plugin's TypeScript projects rely on these compiler options. If a `tsconfig.
 
 ## Troubleshooting
 
+#### `nx build <project>` no longer works for an existing TypeScript library
+
+The first `ts#project` run configures the `@nx/js/typescript` plugin to infer the TypeScript build target as `compile` (the plugin reserves `build` for orchestrating `lint`, `compile` and `test`). Existing libraries relying on the inferred `build` target are inferred as `compile` too — run `nx run <project>:compile`, or use `nx run-many --target build,compile`. Libraries with an explicit `build` target in their `project.json` are unaffected.
+
 #### `The workspace is out of sync`
 
 TypeScript project references need syncing. `init` registers the sync generators; run:

package/docs/get_started/quick-start.mdx

@@ -112,7 +112,7 @@ Open `packages/infra/src/stacks/application-stack.ts` and add the following code
 
 ```typescript
 import { Stack, StackProps } from 'aws-cdk-lib';
-import { DemoApi, DemoWebsite, UserIdentity } from ':my-project/common-constructs';
+import { DemoApi, DemoWebsite, UserIdentity } from '@my-project/common-constructs';
 import { Construct } from 'constructs';
 
 export class ApplicationStack extends Stack {

package/docs/get_started/tutorials/dungeon-game/1.mdx

@@ -202,7 +202,7 @@ import {
 } from '../../core/api/utils.js';
 import { AddCorsPreflightAspect, RestApi } from '../../core/api/rest-api.js';
 import { Procedures, routerToOperations } from '../../core/api/trpc-utils.js';
-import { AppRouter, appRouter } from ':dungeon-adventure/game-api';
+import { AppRouter, appRouter } from '@dungeon-adventure/game-api';
 
 // String union type for all API operation names
 type Operations = Procedures<AppRouter>;
@@ -1091,7 +1091,7 @@ The `ts#infra` generator generates/updates these. Let us examine some of the key
 ```ts
 // packages/infra/src/main.ts
 import { ApplicationStage } from './stages/application-stage.js';
-import { App } from ':dungeon-adventure/common-constructs';
+import { App } from '@dungeon-adventure/common-constructs';
 
 const app = new App();
 

package/docs/get_started/tutorials/dungeon-game/2.mdx

@@ -78,10 +78,10 @@ game -> item: 1..*
 
 The `ts#dynamodb` generator set up [ElectroDB](https://electrodb.dev/en/core-concepts/introduction/), which we will use to model our data. We will persist conversation history in S3, so we add a dependency on the S3 client:
 
-<InstallCommand pkg={getDungeonAdventureElectroDbDependencies()} />
+<InstallCommand pkg={getDungeonAdventureElectroDbDependencies()} project="@dungeon-adventure/game-api" />
 
-<Aside title="Root Dependencies">
-All dependencies are added to the root `package.json` as the `@aws/nx-plugin` follows the [single version policy](https://nx.dev/concepts/decisions/dependency-management#single-version-policy) principle. For more information, refer to the <Link path="guides/typescript-project#dependencies">ts#project guide</Link>.
+<Aside title="Project Dependencies">
+The S3 client is added to the `game-api` project's own `package.json`, since that project's source imports it. Versions are still aligned across the workspace via the package manager's dependency catalog (where supported) ([single version policy](https://nx.dev/concepts/decisions/dependency-management#single-version-policy)). For more information, refer to the <Link path="guides/typescript-project#dependencies">ts#project guide</Link>.
 </Aside>
 
 Replace the generated example entity in `packages/dungeon-db/src/entities/index.ts` with our `Game` and `Inventory` entities, and delete `packages/dungeon-db/src/entities/example.ts`:

package/docs/get_started/tutorials/dungeon-game/overview.mdx

@@ -137,6 +137,7 @@ ddb -> sessions: {
 Before you proceed, you will need the following global dependencies:
 
 <Snippet name="required-prerequisites" />
+- [AWS Credentials](https://docs.aws.amazon.com/sdkref/latest/guide/access.html) configured to your target AWS account, since this tutorial deploys the application and invokes Amazon Bedrock
 - [Docker](https://www.docker.com/) (or [Finch](https://github.com/runfinch/finch)) is required for local DynamoDB development and for building the AgentCore components
 
 :::tip[AI Assistant Setup]

package/docs/guides/agentcore-gateway.mdx

@@ -362,7 +362,7 @@ The AgentCore Gateway generator creates CDK or Terraform infrastructure as code
 The CDK construct for deploying your Gateway lives in the `common/constructs` folder. You can consume this in a CDK application, for example:
 
 ```ts {7} title="packages/infra/src/stacks/application-stack.ts"
-import { MyGateway } from ':my-scope/common-constructs';
+import { MyGateway } from '@my-scope/common-constructs';
 
 export class ApplicationStack extends Stack {
   constructor(scope: Construct, id: string, props?: StackProps) {

package/docs/guides/connection/py-agent-dynamodb.mdx

@@ -58,7 +58,7 @@ To allow the agent's Lambda function to access the DynamoDB table, grant the nec
 <Fragment slot="cdk">
 
 ```ts title="packages/infra/src/stacks/application-stack.ts"
-import { MyTable } from ':my-scope/common-constructs';
+import { MyTable } from '@my-scope/common-constructs';
 
 const table = new MyTable(this, 'Table');
 const myAgent = new MyAgent(this, 'MyAgent');

package/docs/guides/connection/py-agent-rdb.mdx

@@ -73,7 +73,7 @@ The generated agent construct implements `IGrantable` and `IConnectable`, so you
 ```ts title="packages/infra/src/stacks/application-stack.ts"
 import { SecurityGroup } from 'aws-cdk-lib/aws-ec2';
 import { RuntimeNetworkConfiguration } from 'aws-cdk-lib/aws-bedrockagentcore';
-import { MyDatabase } from ':my-scope/common-constructs';
+import { MyDatabase } from '@my-scope/common-constructs';
 
 const db = new MyDatabase(this, 'Db', { vpc, ... });
 

package/docs/guides/connection/py-fast-api-rdb.mdx

@@ -82,7 +82,7 @@ To allow the FastAPI Lambda function to connect to the database at runtime, it m
 In your application stack, deploy the API into the same VPC as the database, then call `allowDefaultPortFrom` and `grantConnect` to open the network path and grant IAM `rds-db:connect` permission to the Lambda handler:
 
 ```ts title="packages/infra/src/stacks/application-stack.ts"
-import { MyDatabase } from ':my-scope/common-constructs';
+import { MyDatabase } from '@my-scope/common-constructs';
 
 const db = new MyDatabase(this, 'Db', { vpc, ... });
 

package/docs/guides/connection/py-mcp-server-dynamodb.mdx

@@ -58,7 +58,7 @@ To allow the MCP server's Lambda function to access the DynamoDB table, grant th
 <Fragment slot="cdk">
 
 ```ts title="packages/infra/src/stacks/application-stack.ts"
-import { MyTable } from ':my-scope/common-constructs';
+import { MyTable } from '@my-scope/common-constructs';
 
 const table = new MyTable(this, 'Table');
 const myMcpServer = new MyMcpServer(this, 'MyMcpServer');

package/docs/guides/connection/py-mcp-server-rdb.mdx

@@ -82,7 +82,7 @@ The generated MCP server construct implements `IGrantable` and `IConnectable`, s
 ```ts title="packages/infra/src/stacks/application-stack.ts"
 import { SecurityGroup } from 'aws-cdk-lib/aws-ec2';
 import { RuntimeNetworkConfiguration } from 'aws-cdk-lib/aws-bedrockagentcore';
-import { MyDatabase } from ':my-scope/common-constructs';
+import { MyDatabase } from '@my-scope/common-constructs';
 
 const db = new MyDatabase(this, 'Db', { vpc, ... });
 

package/docs/guides/connection/smithy-dynamodb.mdx

@@ -42,7 +42,7 @@ The generator updates your Smithy API's `project.json` to add a dependency from
 Import entity factories from the DynamoDB package and use them inside your operation implementations:
 
 ```ts title="packages/api/src/operations/list-examples.ts"
-import { createExampleEntity } from ':my-scope/my-table';
+import { createExampleEntity } from '@my-scope/my-table';
 import {
   ListExamplesOperationInput,
   ListExamplesOperationOutput,

package/docs/guides/connection/smithy-rdb.mdx

@@ -55,7 +55,7 @@ Additionally, it updates the API's `dev` target to start the database automatica
 The generator adds a typed `db` property to `ServiceContext` in `context.ts`:
 
 ```ts title="packages/api/src/context.ts" {1,7}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 export interface ServiceContext {
   tracer: Tracer;
@@ -70,7 +70,7 @@ export interface ServiceContext {
 The Prisma client is instantiated inside `lambdaHandler` and passed through the service context:
 
 ```ts title="packages/api/src/handler.ts" {1,10}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 export const lambdaHandler = async (event: APIGatewayProxyEvent) => {
   const httpRequest = convertEvent(event);
@@ -141,7 +141,7 @@ const httpResponse = await serviceHandler.handle(httpRequest, {
 The generator applies the same Prisma client injection inside the request handler in `local-server.ts`:
 
 ```ts title="packages/api/src/local-server.ts" {1,5,10}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 const server = createServer(async function (req, res) {
   const httpRequest = convertRequest(req);

package/docs/guides/connection/trpc-dynamodb.mdx

@@ -42,7 +42,7 @@ The generator updates your tRPC API's `project.json` to add a dependency from it
 Import entity factories from the DynamoDB package and use them inside your tRPC procedures:
 
 ```ts title="packages/api/src/procedures/example.ts"
-import { createExampleEntity } from ':my-scope/my-table';
+import { createExampleEntity } from '@my-scope/my-table';
 import { publicProcedure } from '../init.js';
 
 export const listExamples = publicProcedure

package/docs/guides/connection/ts-agent-a2a.mdx

@@ -70,7 +70,7 @@ The generator transforms your agent's `agent.ts` to wrap the remote A2A agent as
 
 ```ts title="packages/example/src/my-agent/agent.ts" {2,5-11,14}
 import { Agent, tool } from '@strands-agents/sdk';
-import { RemoteAgentClientStrands } from ':my-scope/agent-connection';
+import { RemoteAgentClientStrands } from '@my-scope/agent-connection';
 import { z } from 'zod';
 
 export const getAgent = async (sessionId: string) => {

package/docs/guides/connection/ts-agent-dynamodb.mdx

@@ -42,7 +42,7 @@ The generator updates the agent's `<agent-name>-dev` target in `project.json` to
 Import entity factories from the DynamoDB package and use them inside your agent definition:
 
 ```ts title="packages/my-service/src/my-agent/agent.ts"
-import { createExampleEntity } from ':my-scope/my-table';
+import { createExampleEntity } from '@my-scope/my-table';
 
 export const getAgent = async () => {
   // ...
@@ -70,7 +70,7 @@ To allow the agent's Lambda function to access the DynamoDB table, grant the nec
 <Fragment slot="cdk">
 
 ```ts title="packages/infra/src/stacks/application-stack.ts"
-import { MyTable } from ':my-scope/common-constructs';
+import { MyTable } from '@my-scope/common-constructs';
 
 const table = new MyTable(this, 'Table');
 const myAgent = new MyAgent(this, 'MyAgent');

package/docs/guides/connection/ts-agent-gateway.mdx

@@ -67,7 +67,7 @@ The generator transforms your agent's `agent.ts` to use the Gateway client:
 
 ```ts title="packages/example/src/my-agent/agent.ts" {2,5,8}
 import { Agent } from '@strands-agents/sdk';
-import { MyGatewayClientStrands } from ':my-scope/agent-connection';
+import { MyGatewayClientStrands } from '@my-scope/agent-connection';
 
 export const getAgent = async () => {
   const myGateway = await MyGatewayClientStrands.create();

package/docs/guides/connection/ts-agent-mcp.mdx

@@ -70,7 +70,7 @@ The generator transforms your agent's `agent.ts` to use the MCP server's tools:
 
 ```ts title="packages/example/src/my-agent/agent.ts" {2,5,8}
 import { Agent, tool } from '@strands-agents/sdk';
-import { MyMcpServerClientStrands } from ':my-scope/agent-connection';
+import { MyMcpServerClientStrands } from '@my-scope/agent-connection';
 
 export const getAgent = async (sessionId: string) => {
   const myMcpServerClient = await MyMcpServerClientStrands.create(sessionId);

package/docs/guides/connection/ts-agent-rdb.mdx

@@ -53,7 +53,7 @@ Additionally, the agent's `<agent-name>-dev` target is updated to depend on the
 The Prisma client is instantiated inside `getAgent()`. Since the `ts#agent` generator configures a single Agent per session, the client is also reused for the lifetime of the session:
 
 ```ts title="packages/my-service/src/my-agent/agent.ts" {1,4}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 export const getAgent = async () => {
   const myDb = await getMyDb();
@@ -67,8 +67,8 @@ export const getAgent = async () => {
 Running the generator again with a different target adds the second database alongside the first:
 
 ```ts title="packages/my-service/src/my-agent/agent.ts" {1,2,5,6}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
-import { getPrisma as getOtherDb } from ':my-scope/other-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
+import { getPrisma as getOtherDb } from '@my-scope/other-db';
 
 export const getAgent = async () => {
   const myDb = await getMyDb();
@@ -88,7 +88,7 @@ The generated agent construct implements `IGrantable` and `IConnectable`, so you
 ```ts title="packages/infra/src/stacks/application-stack.ts"
 import { SecurityGroup } from 'aws-cdk-lib/aws-ec2';
 import { RuntimeNetworkConfiguration } from 'aws-cdk-lib/aws-bedrockagentcore';
-import { MyDatabase } from ':my-scope/common-constructs';
+import { MyDatabase } from '@my-scope/common-constructs';
 
 const db = new MyDatabase(this, 'Db', { vpc, ... });
 

package/docs/guides/connection/ts-mcp-server-dynamodb.mdx

@@ -42,7 +42,7 @@ The generator updates the MCP server's `<mcp-server-name>-dev` target in `projec
 Import entity factories from the DynamoDB package and use them inside `createServer`:
 
 ```ts title="packages/my-service/src/my-mcp/server.ts"
-import { createExampleEntity } from ':my-scope/my-table';
+import { createExampleEntity } from '@my-scope/my-table';
 
 export const createServer = async () => {
   const server = new McpServer({ name: 'my-service', version: '1.0.0' });
@@ -67,7 +67,7 @@ To allow the MCP server to access the DynamoDB table, grant the necessary permis
 <Fragment slot="cdk">
 
 ```ts title="packages/infra/src/stacks/application-stack.ts"
-import { MyTable } from ':my-scope/common-constructs';
+import { MyTable } from '@my-scope/common-constructs';
 
 const table = new MyTable(this, 'Table');
 const myMcpServer = new MyMcpServer(this, 'MyMcpServer');

package/docs/guides/connection/ts-mcp-server-rdb.mdx

@@ -53,7 +53,7 @@ Additionally, the `<mcp-server-name>-dev` target is updated to depend on the dat
 The Prisma client is fetched inside `createServer` and available to all tools and resources registered there:
 
 ```ts title="packages/my-service/src/my-mcp/server.ts" {1,4}
-import { getPrisma as getMyDb } from ':my-scope/my-db';
+import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 export const createServer = async () => {
   const myDb = await getMyDb();
@@ -87,7 +87,7 @@ The generated MCP server construct implements `IGrantable` and `IConnectable`, s
 ```ts title="packages/infra/src/stacks/application-stack.ts"
 import { SecurityGroup } from 'aws-cdk-lib/aws-ec2';
 import { RuntimeNetworkConfiguration } from 'aws-cdk-lib/aws-bedrockagentcore';
-import { MyDatabase } from ':my-scope/common-constructs';
+import { MyDatabase } from '@my-scope/common-constructs';
 
 const db = new MyDatabase(this, 'Db', { vpc, ... });