Build Executor

Builds a FrontMCP project by running frontmcp build from the project root. The node target produces a bundled server; other targets (vercel, lambda, cloudflare) compile with tsc and bundle the result. Code imported through tsconfig path aliases (for example @my-org/shared from a workspace library) is resolved and bundled for every target.

The executor runs the frontmcp CLI installed in your workspace (node_modules/.bin/frontmcp) and never downloads one with npx. Install it with nx add @frontmcp/nx or npm install -D frontmcp.

Usage

nx build my-app

Configuration

project.json

{
  "targets": {
    "build": {
      "executor": "@frontmcp/nx:build",
      "outputs": ["{projectRoot}/dist"],
      "options": {
        "entry": "{projectRoot}/src/main.ts",
        "outputPath": "{projectRoot}/dist"
      }
    }
  }
}

Options

Option	Type	Description
`entry`	`string`	Entry file path
`outputPath`	`string`	Output directory path
`target`	`node` \| `vercel` \| `lambda` \| `cloudflare`	Deployment target (passed to `frontmcp build --target`)
`adapter`	same as `target`	Deprecated alias of `target`; `target` wins when both given

Caching

This executor is cacheable. Projects generated by @frontmcp/nx set "cache": true on the build target, and nx add @frontmcp/nx (the init generator) registers the same for @frontmcp/nx:build and @frontmcp/nx:build-exec in nx.json targetDefaults. Nx skips the build if inputs haven’t changed.

nx.json

{
  "targetDefaults": {
    "build": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    }
  }
}

Get Started

Generators

Executors

Usage

Configuration

Options

Caching

​Usage

​Configuration

​Options

​Caching

Usage

Configuration

Options

Caching