jetson-ai-lab-verify-build

name	jetson-ai-lab-verify-build
description	Run npm run build on jetson-ai-lab and triage Astro content collection / MDX / model frontmatter / benchmarks.json failures after edits. Use when verifying the site builds after content, model, tutorial, benchmark, or asset changes.
license	Apache-2.0
compatibility	Requires Node.js and npm. Run from the repository root where package.json lives.

Jetson AI Lab: verify the build

When to run

Run a full static build after any change to:

• src/content/models/*.md (model catalog frontmatter / Run / Serve / one-shot)
• src/content/tutorials/**/*.{md,mdx}
• src/content/projects/**, src/content/gtc26/**, or any other src/content/ collection
• src/data/benchmarks.json (the model-page benchmark chart joins on this)
• public/ (including public/code-samples/)

When writing or editing tutorials, include authors in frontmatter.

Command

From the repository root (where package.json and astro.config.mjs live):

npm run build

Resolve all errors before merging. The dev server alone is not enough for content-schema issues — the production build is what runs Zod validation across all collections.

---

Common failures

Models collection (Zod / superRefine)

If you see an error path on supported_inference_engines or a message like:

Provide supported_inference_engines and/or serving.entries (non-empty), one_shot_inference commands, or set hide_run_button: true.

Fix the offending file in src/content/models/ per skill jetson-model-catalog-inference: provide either serving.entries, supported_inference_engines, a meaningful one_shot_inference, or set hide_run_button: true.

Models collection (other Zod errors)

Other typical model-page schema failures:

• Invalid url on huggingface_url / build_nvidia_url → must be a full https://... URL, not a slug.
• Required on title, short_description, or precision → these three are the only top-level required fields.
• Type errors on modalities / matrix_modules_disabled / benchmark_series → these must be arrays of strings, not comma-separated text.

benchmark_key mismatch (silent)

The model page joins to src/data/benchmarks.json by benchmark_key === models[].name. A typo does not fail the build — the benchmark chart simply does not render. After adding benchmark_key, open /models/<slug> locally and confirm the chart appears.

Likewise benchmark_series entries silently drop unmatched names.

Benchmark product id mismatches

src/data/benchmarks.json uses different ids from the matrix module list. Valid benchmark product ids are:

t5000, t4000, agx_orin_64gb, orin_nx_16gb, orin_nano_8gb, dgx_spark

If you accidentally use matrix ids (orin_agx_64, orin_nano_8, etc.) inside concurrency1 / concurrency8 / oom / dnr, the build still passes (JSON is not Zod-validated), but the bars / OOM markers don't render. See the matrix-id ↔ product-id table in skill jetson-model-catalog-inference.

MDX / Astro parse errors

Tutorial files under src/content/tutorials/ are MDX. Common parse failures:

• Unescaped $ or {} inside HTML tags mixed with Markdown can break the MDX parser. Keep shell variables inside fenced code blocks when possible, or use HTML entities.
• Stray < characters in inline prose are interpreted as JSX tag opens.

Missing assets

Broken links to /code-samples/... usually mean the file is missing under public/code-samples/ — see skill jetson-ai-lab-code-samples.

---

Source of truth

Item	Path
Build script	package.json (scripts.build)
Astro config	astro.config.mjs
Model validation	src/content/config.ts (models collection superRefine)
Benchmark data file	src/data/benchmarks.json
Model catalog skill	.agents/skills/jetson-model-catalog-inference/SKILL.md
Code samples skill	.agents/skills/jetson-ai-lab-code-samples/SKILL.md