Overview
@noego/app reads your noego.config.yml, starts the server and UI,
hands backend route definitions to Dinner and frontend route definitions to Forge, and builds the app for production.
Think of App as the full-stack runtime shell. It starts Dinner for backend routes and Forge for frontend routes; the details of pages, load functions, and page controllers are covered in the Forge docs.
What App Owns
Runtime orchestration
Loads noego.config.yml, starts the configured services, watches files, and builds dist/.
Backend handoff
Passes server.openapi and controller paths to Dinner for API route validation and dispatch.
Frontend handoff
Passes client.openapi, client.shell, and componentDir to Forge for pages, layouts, loaders, and page controllers.
Frontend Details Live in Forge
App config tells Forge where the UI entry, shell, route definitions, and component directory are. Once those paths are resolved, Forge handles the page system.