AIditorEcosystemDocumentationDesign Log
GitHubGet Started
Production Build
← Documentation
Designer28
Developer13
Plugin Developer20
DevOps6
Contracts5

Production Build

Production Build

DevOpsDevOps Agent Kit — documentation written for AI agents, readable by humans.

Building

jay-stack build
jay-stack build --version 2
jay-stack build --no-minify    # debugging
jay-stack build -v             # verbose output

Version defaults to the version field in package.json (e.g., "1.2.3" → build version 10203). Override with --version.

Build Output Structure

The build produces two directories under build/v{n}/:

build/v{n}/
├── frontend/                        # Browser-facing assets (→ CDN or static serving)
│   ├── shared/                      # Framework + plugin client chunks
│   │   ├── runtime-{hash}.js
│   │   ├── component-{hash}.js
│   │   └── shared-manifest.json
│   ├── pages/                       # Per-page client bundles + CSS
│   │   ├── index/
│   │   │   ├── page-{hash}.js
│   │   │   └── page.css
│   │   └── products/[slug]/
│   │       ├── page_{hash}-{hash}.js
│   │       └── page_{hash}.css
│   └── public/                      # Copied from project ./public
│       └── images/
│           └── logo.png
│
├── backend/                         # Server-only artifacts (→ container)
│   ├── route-manifest.json          # All routes, instances, action registry
│   ├── build-metadata.json          # Version, timestamp, instance count
│   ├── server/                      # Compiled server code
│   │   ├── init.js
│   │   ├── pages/{route}/page.js
│   │   ├── components/{name}/{name}.js
│   │   ├── plugins/{name}/{name}.js
│   │   └── actions/{name}.actions.js
│   └── pre-rendered/                # SSR artifacts per instance
│       └── {route}/
│           ├── page.jay-html            # Pre-rendered HTML template
│           ├── page.cache.json          # Slow ViewState + carryForward
│           ├── page.server-element.js   # Streaming SSR module
│           └── page-parts.json          # Component wiring config

Frontend vs Backend

Directory Contains Deploy to
frontend/ JS bundles, CSS, images — everything the browser loads CDN or static file server
backend/ Server modules, pre-rendered HTML, manifests — everything the server reads Container / server

The build is environment-agnostic. The same output serves any deployment mode. staticBaseUrl (where browser assets are hosted) is a serve-time parameter, not baked into the build.

Manifest

backend/route-manifest.json contains:

  • routes — pattern, segments, server module path, instances with params
  • instances — preRenderedPath and serverElementPath (relative to backend/), clientBundlePath and clientCssPath (relative to frontend/)
  • actions — server module paths, action names
  • sharedManifest — maps package names to hashed filenames in frontend/shared/

Project Structure Requirements

For production builds to work correctly:

  • Headfull FS components must be in src/components/ (not inside page directories)
  • Headless plugins must be in src/plugins/
  • Actions must be in src/actions/ with *.actions.ts naming
  • Init must be at src/init.ts

The build discovers server-side modules from src/pages/, src/components/, src/plugins/, and src/actions/. Files outside these directories are not compiled for server use.

About this document

This page is part of the Jay Stack Agent Kit — documentation generated from the framework source and written primarily for AI agents. The language and structure are optimized for machine consumption — expect precise, specification-style prose rather than narrative documentation. Learn more about the Agent Kit →