# Build And Profiling > Build dependency chains, rebuild sequences, profiling with MCP, and Analysis MCP server setup for Verter Use when this capability is needed. - Skill: `tomevault-io/build-and-profiling` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/build-and-profiling` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/build-and-profiling/raw - Safety review: pending (external: skill-scanner PASS, skillspector WARNING) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/build-and-profiling --- # Build Dependency Chain & Profiling ## Build Dependency Chain When changing Rust code, you must rebuild downstream artifacts in order: ``` verter_core + verter_analysis + verter_host + verter_ffi (Rust crates) ↓ cargo build verter_napi (NAPI-RS cdylib) verter_lsp (LSP binary) verter_wasm (wasm-bindgen cdylib) ↓ pnpm run build:native ↓ pnpm run build:lsp ↓ pnpm run build:wasm @verter/native (.node binary) verter-lsp (target/debug/) @verter/wasm (WASM pkg) ↓ ↓ ↓ @verter/unplugin (bundler) verter-vscode (F5/VSIX) @verter/playground (browser) ↓ playground build (Vite) ↓ playground E2E tests ``` ## Common Rebuild Sequences | What changed | Rebuild commands (in order) | | ------------------------------------- | ------------------------------------------------------------------------------------------------------ | | Rust crate (`verter_core`) | `pnpm run build:native` → rebuild any downstream consumer | | Rust LSP (`verter_lsp`) | `pnpm run build:lsp` (or `build:lsp:release` for optimized) → restart VS Code extension host | | Unplugin (`packages/unplugin`) | `pnpm run build:ts` (or just rebuild unplugin) | | Playground after Rust/unplugin change | `pnpm run build:native` → `cd packages/playground && rm -rf dist node_modules/.vite && npx vite build` | | WASM (for playground browser editor) | `pnpm run build:wasm` | | Everything | `pnpm build` (runs native → lsp → wasm → ts in correct order) | ## Key Details - `@verter/unplugin` depends on `@verter/native` — compiles `.vue` files at build time via the Rust native binary - `@verter/playground` uses `@verter/unplugin` (devDep) for its own Vue SFC compilation, and `@verter/wasm` (dep) for the in-browser editor - The native binary lives in `packages/native/dist/` after `build:native` - The LSP binary lives in `target/debug/verter-lsp` (or `target/release/verter-lsp` with `build:lsp:release`) - Clear Vite cache (`node_modules/.vite`) when rebuilding playground after native changes ## Quick Rebuild (Native) ```bash # Quick rebuild native + copy cargo build --release --package verter_napi && rm -f packages/native/dist/verter-native.win32-x64-msvc.node && cp target/release/verter_napi.dll packages/native/dist/verter-native.win32-x64-msvc.node ``` ## Profiling with Hotpath The `hotpath` feature flag enables `#[hotpath::measure]` annotations on key functions for timing/allocation profiling. It propagates across 7 crates: ``` verter_bench --features hotpath ├── verter_core/hotpath (compile_inner, generate_ide_script, generate_ide_template) ├── verter_host/hotpath (upsert_via_scheduler, ensure_compiled, compile_entry, execute_source) │ ├── verter_analysis/hotpath (build_script_analysis_with_scope) │ ├── verter_scheduler/hotpath (execute_source_stage) │ └── verter_vfs/hotpath (read_file, resolve_import) └── verter_diagnostics/hotpath (lint_inner) ``` ### Core-only profiling Two pipeline modes for compiler-level profiling: ```bash # AST-only pipeline (tokenize → parse → OXC expressions): pnpm run profile:hotpath # Timing hotspots pnpm run profile:hotpath:alloc # Timing + allocation hotspots # Full compile pipeline (tokenize → parse → style → script → template codegen): pnpm run profile:hotpath:full # Timing hotspots pnpm run profile:hotpath:full:alloc # Timing + allocation hotspots ``` ### Host-level profiling (`profile_host` example) Exercises the full host pipeline (upsert → bundler compile → IDE compile → lint) across real project directories from the `verter-test-repos` checkout: ```bash # Without hotpath (wall-clock timing only): cargo run --package verter_bench --example profile_host # With hotpath instrumentation (per-function timing): cargo run --package verter_bench --example profile_host --features hotpath ``` Requires `VERTER_TEST_REPOS` env var or a sibling `verter-test-repos` directory. Processes all `.vue` files in each project subdirectory. ## Analysis MCP Server (`verter_mcp`) The `verter-mcp` binary exposes Verter's full analysis, diagnostics, compilation, and scoring pipeline via MCP. It provides 33 tools for AI agents to deeply understand Vue codebases without reading files directly. ```bash # Build pnpm run build:mcp # Debug build pnpm run build:mcp:release # Release build # Run (stdio — agent spawns as child process) verter-mcp --project-root /path/to/vue-project # Run (HTTP — remote/shared access) verter-mcp --transport http --project-root /path/to/vue-project # Serves at http://localhost:6772/mcp ``` MCP config files are checked in at: - `mcp/verter.mcp.json` (stdio) - `mcp/verter-http.mcp.json` (HTTP) For the full tool catalog and agent workflow guide, see [mcp/README.md](mcp/README.md). ## Meta UI Benchmark The repository-owned real-project component-meta benchmark lives in `packages/benchmark`: ```bash pnpm --filter @verter/benchmark bench:meta:ui:setup pnpm --filter @verter/benchmark bench:meta:ui -- --backends=verter --scenarios=single_cold --limit=2 ``` CI uses `.github/workflows/meta-benchmark.yml` to pin the latest `nuxt/ui` `v4` SHA once, run the backend/scenario matrix, and aggregate JSON artifacts into one markdown report. --- > Source: [pikax/verter](https://github.com/pikax/verter) — distributed by [TomeVault](https://tomevault.io).