@aws/nx-plugin-mcp 1.0.0-rc.93 → 1.0.0-rc.95

package/bin/aws-nx-mcp.js

@@ -22000,7 +22000,6 @@ const NX_VERSION = {
 	"class-variance-authority": "0.7.1",
 	clsx: "2.1.1",
 	commander: "15.0.0",
-	"cpy-cli": "7.0.0",
 	electrodb: "3.9.3",
 	esbuild: "0.28.2",
 	"event-source-polyfill": "1.0.31",
@@ -22016,10 +22015,8 @@ const NX_VERSION = {
 	husky: "9.1.7",
 	"fs-extra": "11.4.0",
 	"@types/fs-extra": "11.0.4",
-	"make-dir-cli": "4.0.0",
 	mariadb: "3.5.3",
 	mise: "2026.8.14",
-	ncp: "2.0.0",
 	npm: "12.0.2",
 	"npm-check-updates": "23.1.0",
 	"oidc-client-ts": "3.5.0",
@@ -22028,9 +22025,9 @@ const NX_VERSION = {
 	"react-oidc-context": "3.3.1",
 	react: "19.2.8",
 	"react-dom": "19.2.8",
-	rimraf: "6.1.3",
 	rolldown: "1.2.6",
 	"rolldown-plugin-dts": "0.28.3",
+	shx: "0.4.0",
 	"simple-git": "3.36.0",
 	"source-map-support": "0.5.21",
 	"starlight-blog": "0.29.0",

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

@@ -117,7 +117,9 @@ If this is the first CDK deployment in your AWS account/region, bootstrap it fir
 
 The `deploy-sandbox` target deploys the sandbox stage defined in `packages/infra/src/main.ts`.
 
-Your first deployment will take around 6 minutes to complete as it waits for all resources to fully stabilize. Subsequent deployments are faster. To speed up iteration during development you can opt into [CloudFormation express mode](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-express-mode.html) by passing the `--express` flag, which completes each resource operation as soon as its configuration is applied rather than waiting for full stabilization.
+The `deploy-sandbox` target uses [CloudFormation express mode](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-express-mode.html), which completes each resource operation as soon as its configuration is applied rather than waiting for full stabilization. Your first deployment will take around 4 minutes to complete, and some resources (such as the CloudFront distribution) may continue provisioning in the background for a short while afterwards. Subsequent deployments are faster.
+
+Because express mode returns before resources have fully stabilized, `deploy-sandbox` is for development only. Use the `deploy-ci` target for CI/CD and production deployments, which always waits for full stabilization.
 
 Once the deployment completes, you will see outputs similar to the following:
 
@@ -127,7 +129,9 @@ dungeon-adventure-infra-sandbox-Application: deploying... [2/2]
 
  ✅  dungeon-adventure-infra-sandbox-Application
 
-✨  Deployment time: 354s
+✨  Deployment time: 220s
+
+⚠️  Stack deployed using Express Mode. Resources still stabilizing: GameUICloudfrontDistribution, UserIdentityWebAcl, ...and more...
 
 Outputs:
 dungeon-adventure-infra-sandbox-Application.GameApiEndpointXXX = https://xxx.execute-api.region.amazonaws.com/prod/

package/docs/guides/docker-bundling.mdx

@@ -5,6 +5,7 @@ description: Build and deploy Docker images for TypeScript and Python projects i
 
 import { FileTree, Tabs, TabItem, Code } from '@astrojs/starlight/components';
 import NxCommands from '@components/nx-commands.astro';
+import InstallCommand from '@components/install-command.astro';
 import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 import Link from '@components/link.astro';
 import Infrastructure from '@components/infrastructure.astro';
@@ -18,9 +19,9 @@ export const trivyTarget = `{
       "executor": "nx:run-commands",
       "options": {
         "commands": [
-          "rimraf dist/packages/my-project/trivy",
-          "make-dir dist/packages/my-project/trivy",
-          "ncp packages/my-project/.trivyignore dist/packages/my-project/trivy/.trivyignore",
+          "shx rm -rf dist/packages/my-project/trivy",
+          "shx mkdir -p dist/packages/my-project/trivy",
+          "shx cp packages/my-project/.trivyignore dist/packages/my-project/trivy/.trivyignore",
           "docker save -o dist/packages/my-project/trivy/image.tar my-scope-my-project:latest",
           "docker run --rm -v \\"./dist/packages/my-project/trivy\\":/scan public.ecr.aws/aquasecurity/trivy:${CONTAINER_VERSIONS.trivy} image --input /scan/image.tar --ignorefile /scan/.trivyignore --scanners vuln --severity HIGH,CRITICAL --ignore-unfixed --exit-code 1 --no-progress -q"
         ],
@@ -170,7 +171,7 @@ Add a `docker` target which:
       "executor": "nx:run-commands",
       "options": {
         "commands": [
-          "ncp packages/my-project/src/Dockerfile dist/packages/my-project/bundle/Dockerfile",
+          "shx cp packages/my-project/src/Dockerfile dist/packages/my-project/bundle/Dockerfile",
           "docker build --platform linux/arm64 -t my-scope-my-project:latest dist/packages/my-project/bundle"
         ],
         "parallel": false
@@ -186,7 +187,9 @@ Set `"cache": false` on image build targets. A built image is not written to an
 :::
 
 :::tip[Cross-platform file copy]
-The `ncp` package provides a cross-platform file/directory copy command, avoiding `cp` (unavailable on Windows). Install it at the root of your workspace with `pnpm add -D -w ncp`.
+The `shx` package provides cross-platform `cp`, `rm` and `mkdir` commands, avoiding the shell builtins (unavailable on Windows). Install it at the root of your workspace:
+
+<InstallCommand pkg="shx" dev />
 :::
 
 Running this target produces a local image tagged `my-scope-my-project:latest`, built from the minimal context at `dist/packages/my-project/bundle/`:
@@ -263,10 +266,10 @@ Add a `docker` target which copies the `Dockerfile` into the bundle output direc
       "executor": "nx:run-commands",
       "options": {
         "commands": [
-          "rimraf dist/packages/my-project/docker",
-          "make-dir dist/packages/my-project/docker",
-          "ncp dist/packages/my-project/bundle-arm dist/packages/my-project/docker",
-          "ncp packages/my-project/src/Dockerfile dist/packages/my-project/docker/Dockerfile",
+          "shx rm -rf dist/packages/my-project/docker",
+          "shx mkdir -p dist/packages/my-project/docker",
+          "shx cp -R dist/packages/my-project/bundle-arm/. dist/packages/my-project/docker",
+          "shx cp packages/my-project/src/Dockerfile dist/packages/my-project/docker/Dockerfile",
           "docker build --platform linux/arm64 -t my-scope-my-project:latest dist/packages/my-project/docker"
         ],
         "parallel": false

package/docs/guides/typescript-infrastructure.mdx

@@ -379,11 +379,11 @@ For more details, please refer to the [CDK bootstrapping documentation](https://
 
 Your project has three deploy targets, each suited to a different situation:
 
-| Target           | Use it for                                                                       |
-| ---------------- | -------------------------------------------------------------------------------- |
-| `deploy-sandbox` | Deploying your own sandbox stage during development. No stage argument needed.    |
-| `deploy`         | Deploying any stage, by naming the stage or stacks you want.                      |
-| `deploy-ci`      | Deploying from a CI/CD pipeline, using a pre-synthesized cloud assembly.          |
+| Target           | Use it for                                                                                             |
+| ---------------- | ------------------------------------------------------------------------------------------------------ |
+| `deploy-sandbox` | Deploying your own sandbox stage during development. No stage argument needed. Uses express mode.        |
+| `deploy`         | Deploying any stage, by naming the stage or stacks you want.                                            |
+| `deploy-ci`      | Deploying from a CI/CD pipeline, using a pre-synthesized cloud assembly. Waits for full stabilization.   |
 
 `deploy-sandbox` and `deploy` depend on `^assemble`, so they build the artifacts they are about to deploy and nothing else. `deploy-ci` deploys an assembly your pipeline already built, so it has no build dependencies at all.
 
@@ -402,11 +402,11 @@ The `deploy-sandbox` target deploys the sandbox stage that `main.ts` declares, s
 This is the quickest way to get your own copy of the application running in AWS while you develop.
 
 :::tip[Express Mode for Faster Deployments]
-The deploy targets wait for full resource stabilization by default, favouring consistency over speed. To speed up iteration during development, opt into [CloudFormation express mode](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-express-mode.html) by passing CDK's `--express` flag:
+The `deploy-sandbox` target uses [CloudFormation express mode](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-express-mode.html) by default (via CDK's `--express` flag). Express mode finishes once resource configuration is confirmed applied rather than waiting for full stabilization, with propagation continuing in the background, for significantly faster iteration cycles.
 
-<NxCommands commands={['deploy-sandbox <my-infra> --express']} />
+Since it returns before resources have finished stabilizing, express mode suits the sandbox stage you iterate on, not CI/CD or production deployments — use [`deploy-ci`](#deploying-to-aws-in-a-cicd-pipeline) for those. To wait for full resource stabilization here too, pass `--no-express`:
 
-Express mode finishes once resource configuration is confirmed applied rather than waiting for full stabilization, with propagation continuing in the background, for significantly faster iteration cycles. It is intended for development and iteration.
+<NxCommands commands={['deploy-sandbox <my-infra> --no-express']} />
 :::
 
 ### Deploying a Specific Stage
@@ -419,13 +419,15 @@ You can specify any stage so long as it is defined in `main.ts`. To deploy an in
 
 <NxCommands commands={['deploy <my-infra> <my-infra>-sandbox/Application']} />
 
+Since this target can name any stage, including your production one, it waits for full resource stabilization when you generate with `stageConfig`. Pass `--express` to opt into express mode for a stage you are iterating on.
+
 ## Deploying to AWS in a CI/CD Pipeline
 
 Use the `deploy-ci` target if you are deploying to AWS as part of a CI/CD pipeline.
 
 <NxCommands commands={['deploy-ci <my-infra> my-stage/*']} />
 
-This target differs slightly from the regular `deploy` target in that it deploys a pre-synthesized cloud assembly rather than synthesizing on the fly. This avoids potential non-determinism from package version changes, ensuring that every pipeline stage deploys using the same cloud assembly.
+This target differs from the `deploy` and `deploy-sandbox` targets in two ways. First, it deploys a pre-synthesized cloud assembly rather than synthesizing on the fly, avoiding potential non-determinism from package version changes and ensuring that every pipeline stage deploys using the same cloud assembly. Second, it never uses express mode, so it always waits for every resource to fully stabilize before reporting success.
 
 ## Tearing Down AWS Infrastructure
 

package/package.json

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