Skip to main content
nx-workspace-expert Deep Nx monorepo expertise including CNW workspace creation, executors, Docker plugin, migrations, and process spawning. Use for Nx workspace issues, creating workspaces, understanding executor behavior, debugging Nx-specific problems, or Docker builds. Triggers on "Nx", "workspace", "CNW", "create-nx-workspace", "executor", "nx migrate", "nx docker".
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/jaysoo/dot-ai-config --skill nx-workspace-expertLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Métiers associés SOC
Basé sur la classification professionnelle SOC
name nx-workspace-expert description Deep Nx monorepo expertise including CNW workspace creation, executors, Docker plugin, migrations, and process spawning. Use for Nx workspace issues, creating workspaces, understanding executor behavior, debugging Nx-specific problems, or Docker builds. Triggers on "Nx", "workspace", "CNW", "create-nx-workspace", "executor", "nx migrate", "nx docker".
Nx Workspace Expert
Acronyms
CNW : Create Nx Workspace (packages/create-nx-workspace/)CNP : Create Nx Plugin (packages/create-nx-plugin/)NXC : Nx CLI team issues (Linear)DOC : Documentation team issuesCLOUD : Nx Cloud team issues
Create Nx Workspace (CNW)
Basic Usage
npx create-nx-workspace@latest
npx -y create-nx-workspace@latest myworkspace --preset=react-monorepo --no-interactive
npx -y create-nx-workspace@latest
Common Presets
Preset Description react-monorepoReact apps + shared libs angular-monorepoAngular apps + shared libs node-monorepoNode.js apps (Express, Nest) vue-monorepoVue apps + shared libs react-standaloneSingle React app
Useful Options --packageManager=pnpm
--no-interactive
--appName=api
--framework=nest
--e2eTestRunner=playwright
--unitTestRunner=vitest
--nxCloud=skip
--docker
Testing/Debugging Pattern cd /tmp
npx -y create-nx-workspace@latest testworkspace \
--preset=node-monorepo \
--appName=api \
--framework=nest \
--no-interactive \
--nx-cloud=skip
Executor Code Paths
run-commands Spawning Logic Location : packages/nx/src/executors/run-commands/run-commands.impl.ts:130-163
Condition Code Path Spawning Method Single command + PTY supported runSingleCommandWithPseudoTerminal()PTY (Rust native) Parallel commands ParallelRunningTasksNode exec() with piped stdio Serial commands SeriallyRunningTasksPTY if supported
PTY Check Conditions (lines 130-138) const isSingleCommandAndCanUsePseudoTerminal =
isSingleCommand &&
usePseudoTerminal &&
process.env .NX_NATIVE_COMMAND_RUNNER !== 'false' &&
!normalized.commands [0 ].prefix &&
normalized.usePty ;
Key Files
run-commands.impl.ts - Entry point with routing logicrunning-tasks.ts - Task runner implementationspseudo-terminal.ts - PTY wrapper for Rust bindingspackages/nx/src/native/ - Rust native bindings
Debugging Code Paths Don't assume - verify with logging in node_modules:
console .log ('CODE PATH:' , 'runSingleCommandWithPseudoTerminal' );
Nx Docker Plugin (@nx/docker)
Target Naming Use docker:build NOT docker-build
Dockerfile Requirements
MUST be named exactly Dockerfile (not *.dockerfile)
Located in project root directory
Minimal Configuration {
"docker:build" : {
"options" : {
"cwd" : "" ,
"file" : "apps/myapp/Dockerfile"
}
}
}
No executor needed (inferred by plugin)
nx-release-publish target is auto-inferred
Sub-Projects for Multiple Images apps/myapp/
├── project.json
├── Dockerfile
└── executor/
├── project.json # Separate project
└── Dockerfile
Migration Testing
NEVER Use Tags
npx nx migrate @next
npx nx migrate 22.0.0-beta.7
Complete Migration Process
npx nx migrate 22.0.0
pnpm install
npx nx migrate --run-migrations
cat package.json | grep '"nx"'
Why Tags Are Dangerous
@next points to next major (v23), not current beta (v22)Always verify: npm view nx@next version
Common Issues & Fixes
Stuck Processes lsof -i :PORT | grep LISTEN
kill PID
After Modifying package.json ALWAYS run nx sync - updates inferred targets
1. Modify package.json
2. nx sync
3. git add && git commit
File Reversions Usually linting/formatting. Verify with git diff.
TSC Errors in Isolation Normal - use project-level checks: nx run PROJECT:typecheck
Testing Conventions
File Extensions Use .spec.ts NOT .test.ts
Vitest Config
import { defineConfig } from 'vitest/config' ;
export default defineConfig ({
test : {
globals : true ,
environment : 'node' ,
include : ['src/**/*.{test,spec}.{js,ts,jsx,tsx}' ],
}
});
Nx Vite Plugin Add project to nx.json Vite plugin includes for inferred targets.
GitHub Actions Notes
setup-node Side Effects setup-node with registry-url sets NODE_AUTH_TOKEN (even dummy placeholder).
When migrating away (e.g., to mise), this side effect is lost.
NPM Trusted Publisher (OIDC)
Uses id-token: write permission
No token secrets needed
CI detection should use GITHUB_ACTIONS env var
Key Package Locations Package Location CNW packages/create-nx-workspace/CNP packages/create-nx-plugin/Core Nx packages/nx/run-commands packages/nx/src/executors/run-commands/PTY bindings packages/nx/src/native/
Investigation Best Practices
Verify code path FIRST - don't assumeAdd logging to node_modules to confirm executionCheck for feature flags/env vars that change behaviorWatch for multiple implementations :
Single vs parallel commands
PTY vs spawn vs exec
Native (Rust) vs JavaScript
Plus depuis ce dépôt Check modified Nx documentation pages against the astro-docs style guide. Auto-trigger after writing or editing docs content in the nx repo. Also trigger on "check style", "style guide", "docs review", "validate docs". Should run as a final step whenever docs files are modified.
Smoke-test the locally built create-nx-workspace CLI end-to-end against the real npm registry, optionally simulating blocked github.com egress (sandboxed AI agents). Packs the built package, pins its version to a published nx so the sandbox install works, and runs scenario commands with a fetch shim + diverted telemetry. Use when changing CNW download/preset/error flows and needing live proof beyond unit tests. Triggers: "smoke test CNW", "run the CNW dist smoke", "test create-nx-workspace locally", "simulate blocked github", "verify the CNW error path live".
Query and analyze create-nx-workspace (CNW) telemetry data from MongoDB. Supports prod and staging environments. Use for error analysis, funnel metrics, version comparisons, and usage trends. Triggers on "CNW stats", "workspace stats", "error rates", "telemetry", "commandStats", "CNW errors", "CNW analysis". Also triggers on "show CNW UI", "CNW dashboard", "CNW report", "show me visually" — generates a self-contained HTML dashboard from the bundled template.
