nx-workspace

por nrwl

Explorar y comprender espacios de trabajo de Nx. ÚSALO al responder preguntas sobre el espacio de trabajo, proyectos o tareas. TAMBIÉN ÚSALO cuando un comando de nx falle o necesites verificar objetivos/configuración disponibles antes de ejecutar una tarea. EJEMPLOS: '¿Qué proyectos hay en este espacio de trabajo?', '¿Cómo está configurado el proyecto X?', '¿Qué depende de la biblioteca Y?', '¿Qué objetivos puedo ejecutar?', 'No se puede encontrar la configuración para la tarea', 'depurar fallo de tarea de nx'.

npx skills add https://github.com/nrwl/nx-ai-agents-config --skill nx-workspace

Nx Workspace Exploration

This skill provides read-only exploration of Nx workspaces. Use it to understand workspace structure, project configuration, available targets, and dependencies.

Keep in mind that you might have to prefix commands with npx/pnpx/yarn if nx isn't installed globally. Check the lockfile to determine the package manager in use.

Listing Projects

Use nx show projects to list projects in the workspace.

The project filtering syntax (-p/--projects) works across many Nx commands including nx run-many, nx release, nx show projects, and more. Filters support explicit names, glob patterns, tag references (e.g. tag:name), directories, and negation (e.g. !project-name).

# List all projects
nx show projects

# Filter by pattern (glob)
nx show projects --projects "apps/*"
nx show projects --projects "shared-*"

# Filter by tag
nx show projects --projects "tag:publishable"
nx show projects -p 'tag:publishable,!tag:internal'

# Filter by target (projects that have a specific target)
nx show projects --withTarget build

# Combine filters
nx show projects --type lib --withTarget test
nx show projects --affected --exclude="*-e2e"
nx show projects -p "tag:scope:client,packages/*"

# Negate patterns
nx show projects -p '!tag:private'
nx show projects -p '!*-e2e'

# Output as JSON
nx show projects --json

Project Configuration

Use nx show project <name> --json to get the full resolved configuration for a project.

Important: Do NOT read project.json directly - it only contains partial configuration. The nx show project --json command returns the full resolved config including inferred targets from plugins.

You can read the full project schema at node_modules/nx/schemas/project-schema.json to understand nx project configuration options.

# Get full project configuration
nx show project my-app --json

# Extract specific parts from the JSON
nx show project my-app --json | jq '.targets'
nx show project my-app --json | jq '.targets.build'
nx show project my-app --json | jq '.targets | keys'

# Check project metadata
nx show project my-app --json | jq '{name, root, sourceRoot, projectType, tags}'

Target Information

Targets define what tasks can be run on a project.

# List all targets for a project
nx show project my-app --json | jq '.targets | keys'

# Get full target configuration
nx show project my-app --json | jq '.targets.build'

# Check target executor/command
nx show project my-app --json | jq '.targets.build.executor'
nx show project my-app --json | jq '.targets.build.command'

# View target options
nx show project my-app --json | jq '.targets.build.options'

# Check target inputs/outputs (for caching)
nx show project my-app --json | jq '.targets.build.inputs'
nx show project my-app --json | jq '.targets.build.outputs'

# Find projects with a specific target
nx show projects --withTarget serve
nx show projects --withTarget e2e

Workspace Configuration

Read nx.json directly for workspace-level configuration. You can read the full project schema at node_modules/nx/schemas/nx-schema.json to understand nx project configuration options.

# Read the full nx.json
cat nx.json

# Or use jq for specific sections
cat nx.json | jq '.targetDefaults'
cat nx.json | jq '.namedInputs'
cat nx.json | jq '.plugins'
cat nx.json | jq '.generators'

Key nx.json sections:

  • targetDefaults - Default configuration applied to all targets of a given name
  • namedInputs - Reusable input definitions for caching
  • plugins - Nx plugins and their configuration
  • ...and much more, read the schema or nx.json for details

Affected Projects

If the user is asking about affected projects, read the affected projects reference for detailed commands and examples.

Common Exploration Patterns

"What's in this workspace?"

nx show projects
nx show projects --type app
nx show projects --type lib

"How do I build/test/lint project X?"

nx show project X --json | jq '.targets | keys'
nx show project X --json | jq '.targets.build'

"What depends on library Y?"

# Use the project graph to find dependents
nx graph --print | jq '.graph.dependencies | to_entries[] | select(.value[].target == "Y") | .key'

Programmatic Answers

When processing nx CLI results, use command-line tools to compute the answer programmatically rather than counting or parsing output manually. Always use --json flags to get structured output that can be processed with jq, grep, or other tools you have installed locally.

Listing Projects

nx show projects --json

Example output:

["my-app", "my-app-e2e", "shared-ui", "shared-utils", "api"]

Common operations:

# Count projects
nx show projects --json | jq 'length'

# Filter by pattern
nx show projects --json | jq '.[] | select(startswith("shared-"))'

# Get affected projects as array
nx show projects --affected --json | jq '.'

Project Details

nx show project my-app --json

Example output:

{
  "root": "apps/my-app",
  "name": "my-app",
  "sourceRoot": "apps/my-app/src",
  "projectType": "application",
  "tags": ["type:app", "scope:client"],
  "targets": {
    "build": {
      "executor": "@nx/vite:build",
      "options": { "outputPath": "dist/apps/my-app" }
    },
    "serve": {
      "executor": "@nx/vite:dev-server",
      "options": { "buildTarget": "my-app:build" }
    },
    "test": {
      "executor": "@nx/vite:test",
      "options": {}
    }
  },
  "implicitDependencies": []
}

Common operations:

# Get target names
nx show project my-app --json | jq '.targets | keys'

# Get specific target config
nx show project my-app --json | jq '.targets.build'

# Get tags
nx show project my-app --json | jq '.tags'

# Get project root
nx show project my-app --json | jq -r '.root'

Project Graph

nx graph --print

Example output:

{
  "graph": {
    "nodes": {
      "my-app": {
        "name": "my-app",
        "type": "app",
        "data": { "root": "apps/my-app", "tags": ["type:app"] }
      },
      "shared-ui": {
        "name": "shared-ui",
        "type": "lib",
        "data": { "root": "libs/shared-ui", "tags": ["type:ui"] }
      }
    },
    "dependencies": {
      "my-app": [
        { "source": "my-app", "target": "shared-ui", "type": "static" }
      ],
      "shared-ui": []
    }
  }
}

Common operations:

# Get all project names from graph
nx graph --print | jq '.graph.nodes | keys'

# Find dependencies of a project
nx graph --print | jq '.graph.dependencies["my-app"]'

# Find projects that depend on a library
nx graph --print | jq '.graph.dependencies | to_entries[] | select(.value[].target == "shared-ui") | .key'

Troubleshooting

"Cannot find configuration for task X:target"

# Check what targets exist on the project
nx show project X --json | jq '.targets | keys'

# Check if any projects have that target
nx show projects --withTarget target

"The workspace is out of sync"

nx sync
nx reset  # if sync doesn't fix stale cache

Skills relacionadas

assessing-external-test-risk
streamlit
Evalúa si los cambios en una rama o PR son de alto riesgo para el uso de Streamlit alojado externamente o incrustado, y recomienda si la cobertura e2e externa con…
official
tasks
triggerdotdev
Construye agentes de IA, flujos de trabajo y tareas de fondo duraderas con Trigger.dev. Úsalo al crear tareas, activar trabajos, manejar reintentos, programar trabajos cron, o…
official
seedance-v2
agentspace-so
We need to translate the given text from English to Spanish. The text is a description of an agent skill for generating cinematic short-form video using ByteDance Seedance 2.0 Pro on RunComfy. The name "seedance-v2" is to be preserved, but it appears in the text as "seedance-v2" in the CLI command. Also note the list of trigger words at the end: "seedance", "seedance 2", "seedance v2", "seedance..." - these should be preserved as they are likely technical terms or product names. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. So "ByteDance Seedance 2.0 Pro", "RunComfy", "HappyHorse 1.0", "Wan 2.7", "Kling", "runcomfy run bytedance/seedance-v2/pro" should remain as is. Also the duration "4–15s" should be preserved. The text inside <text> is the only
creativevideomedia
reg-feed-watcher
anthropic
Revisa los feeds regulatorios ahora e informa qué hay de nuevo desde la última revisión, filtrado por tu umbral de materialidad. Úsalo cuando el usuario diga "revisa los feeds",…
official
upstash-redis-js
upstash
Trabaja con el SDK de Upstash Redis para TypeScript/JavaScript para operaciones serverless de Redis. Úsalo para almacenamiento en caché, almacenamiento de sesiones, limitación de velocidad, tablas de clasificación, texto completo…
official
arize-link
github
Generar enlaces profundos a la interfaz de usuario de Arize. Úselo cuando el usuario quiera una URL en la que se pueda hacer clic para abrir o compartir un trace, span, sesión, conjunto de datos, cola de etiquetado específicos,…
official
drive-discussion
prisma
Coloca al agente en un modo estructurado de preguntas y respuestas que itera con el usuario hacia una comprensión completa de un tema, luego documenta el resultado (especificación del proyecto,…
official
installation
huggingface
Cómo instalar prime-rl y sus dependencias opcionales. Úselo al configurar el proyecto, instalar extras como deep-gemm para modelos FP8 o solucionar problemas…
official