DEVELOPMENT / CLI

Dowe Dev

Compile the current project, start the targets you choose, and keep development artifacts inside the disposable .dowe directory.

1 / ONE DEVELOPMENT ENTRYPOINT

Start the project from its root

Run Dowe from the directory that contains main.dowe. In a terminal, dowe dev opens the target selector; explicit flags make the same workflow deterministic for scripts and CI.

dowe
dowe dev
dowe dev --target server --target web
dowe dev --target desktop
dowe dev --target android
dowe dev --target ios
Mode
Choice
Behavior

No data

There are no records to display

2 / TARGET PIPELINE

One source model, several targets

The shared Dowe compiler reads the project model once and prepares the selected target pipelines. A fullstack project commonly starts the server and web targets together.

Selection
Outcome
What happens

No data

There are no records to display

3 / DISPOSABLE DEVELOPMENT OUTPUT

Inspect generated support without owning it

Dowe writes generated development output below .dowe, including target manifests, route data, fonts, icon copies, and type-checking support. Keep project source in main.dowe, theme.dowe, views, and server; do not edit generated files.

dowe
.dowe/
  dev/
  apps/
  fonts/
  icons/
  types/
  tsconfig.json

Dowe does not require Node.js, node_modules, Tailwind, or a JavaScript application runtime to compile source or run the Dowe-owned development server.

Web output uses a content-addressed router and design core plus route-selected style and runtime capabilities. Navigation loads missing CSS before replacing content, keeps active styles attached, and retires obsolete route chunks without an unstyled frame.

In dowe dev --target web, enable the in-page Dowe inspector to hover or select a Section, AppBar, or component and see its project-relative source path and inclusive lines. Drag the floating inspector control away from the component when needed. Generated text wrappers inherit their parent component identity, keeping Section, Title, and component mappings precise. The inspector manifest and selection state stay under .dowe and are never emitted by dowe deploy.

Read View Inspector docs

4 / WATCH AND RELOAD

Keep the session open while source changes

The development session watches project inputs, runs the shared rebuild pipeline, and reports successful or failed rebuilds. Web changes reload the browser; server changes restart the backend when the new build succeeds.

Rule
What to remember

No data

There are no records to display

Read Hot Reload docs