Build and emit

Summary

Most workflows stay on .point source plus point check and point launch. Use the commands on this page when something outside Point imports compiled files from generated/.

Do not hand-edit build output. Repair .point and rebuild.

Build decision tree

Pick one path — do not memorize every emit command:

You have…	Command	Output
Logic, actions, routes (JS host)	`point build`	`generated/*.js`
Full-stack app (UI + API + dist)	`point build-app`	`generated/` + `dist/`
Records → database schema	`point build-schema`	SQL migrations
React/Vite host wants `.ts`	`point build-ts`	`generated/*.ts` (advanced)
Python automation scripts	`point build-py`	`generated/*.py` (advanced, no UI/views)
Compiler tooling / debugging	`point build-ast`	AST JSON (internal)

Default: JavaScript. You author .point; the host runs generated JS unless you opt into TS or Python.

Default build

point build myfile.point generated/myfile.js
point build --production myfile.point generated/myfile.js

Use for Bun/Node hosts. Add --production for deploy-oriented output — see Deploy.

Batch:

point build-all

Typed build (optional)

point build-ts myfile.point generated/myfile.ts
point build-ts-all

Use when a host stack wants .ts imports or tsc in CI.

Python build (optional, advanced)

point build-py examples/math.point generated/math.py
point build-py-all

Covers logic, actions, routes, workflows, and commands where a Python runtime consumes output. Application UI, views, and most client code still use the default JavaScript build. See Python build (build-py) for run examples (including examples/tools/process-runner.point) and std bridge details.

AST output (tooling)

point build-ast myfile.point generated/myfile.ast.json