Frontend Scripts

This guide explains the main Zova script workflows in the Cabloy monorepo.

Shared rule

Zova can build SSR, SPA, Web, and Admin modes in one codebase. In Cabloy, contributors should usually start from the root scripts first, then drop into zova/package.json only when they need edition-specific detail.

Detect the edition first

Before choosing script examples, detect whether you are working in Cabloy Basic or Cabloy Start.

A practical rule is:

1. detect the edition first
2. then choose the correct script, flavor, and appMode path
3. only then document or automate edition-specific frontend examples

For the edition-detection workflow, also see Edition Detection.

Cabloy Basic root wrappers

From the current root repository:

npm run dev:zova:admin
npm run dev:zova:web
npm run build:zova

These map to Basic-specific Zova flavors in this repository.

Zova script model

The underlying Zova package still organizes scripts around app mode and flavor.

Examples from the current source include:

• dev:ssr:admin
• build:ssr:admin
• preview:ssr:admin
• dev:ssr:web
• build:ssr:web
• preview:ssr:web
• dev:ssr:cabloyBasicAdmin
• build:ssr:cabloyBasicAdmin
• build:rest:cabloyBasicAdmin
• dev:ssr:cabloyBasicWeb
• build:ssr:cabloyBasicWeb
• build:rest:cabloyBasicWeb

Cabloy Basic

The current public repository documents and scripts support Basic-specific flavors such as:

• cabloyBasicAdmin
• cabloyBasicWeb

Representative Zova commands inside this repo include:

cd zova && npm run dev:ssr:cabloyBasicAdmin
cd zova && npm run build:ssr:cabloyBasicAdmin
cd zova && npm run build:rest:cabloyBasicAdmin

Cabloy Start

The sibling cabloy-start repository is the private commercial edition and uses Start-specific flavors such as:

• cabloyStartAdmin
• cabloyStartWeb

Those commands are not driven by the current Basic repo root wrappers, so verify the Start repo’s package.json, suites, SSR site baselines, and project assets before documenting or automating them.

Workflow guidance

When documenting or automating frontend scripts:

• start from root wrappers for normal Cabloy Basic workflows
• detect the edition before choosing flavor-specific examples
• verify the exact flavor before writing edition-specific examples
• use REST/type generation commands deliberately when backend integration depends on them
• understand the mode/appMode/flavor model before changing script families; see Environment and Config Guide
• enable or package frontend mock support deliberately when development depends on fake-server behavior; see Mock Guide
• use Frontend Quickstart when the reader first needs the end-to-end onboarding story rather than only a script reference