Part Main

Overview

The part-main schematic reads the .nanoforge/{part}.save.json file produced by part-base and generates a fully wired main.ts (or main.js) entry point. It registers all libraries, components, systems, and entities declared in the save file.

Usage

schematics @nanoforge-dev/schematics:part-main --part=client

Options

Option	Type	Default	Description
`part`	`"client" \| "server"`	(required)
`directory`	`string`	`.`
`language`	`"ts" \| "js"`	`ts`	Language of the generated entry point
`initFunctions`	`boolean`	`false`
`saveFile`	`string`	—
`outFile`	`string`	—
`editor`	`boolean`	`false`

Output path resolution

The generated file is placed at one of the following paths, in priority order:

outFile — if provided explicitly
.nanoforge/editor/{part}/main.{language} — if editor: true
{part}/main.{language} — default

How it works

part-main reads {directory}/.nanoforge/{part}.save.json, builds the full application bootstrap code, then writes the result as the entry point. Every time you add a component, system, or entity through the NanoForge CLI or editor, regenerating part-main keeps the entry point in sync with the save file.

Examples

Generate a client main file:

schematics @nanoforge-dev/schematics:part-main --part=client

Generate a server main file with init hooks:

schematics @nanoforge-dev/schematics:part-main \
  --part=server \
  --initFunctions=true

Generate with a custom save file and output path:

schematics @nanoforge-dev/schematics:part-main \
  --part=client \
  --saveFile=./custom.save.json \
  --outFile=./src/client/main.ts

Regenerate the editor entry point:

schematics @nanoforge-dev/schematics:part-main \
  --part=client \
  --editor=true

Commands

Configuration

Getting-Started

Schematics

Overview

Usage

Options

Output path resolution

How it works

Examples

​Overview

​Usage

​Options

​Output path resolution

​How it works

​Examples

Overview

Usage

Options

Output path resolution

How it works

Examples