JARVIGManual

Hosts

HostShips asCallsMust not include
EditorJARVIGEditor native processEngine APIs, then draws panelsIts own importer, cooker, or renderer
PlayerMyGame plus the runtime library, or a static linkEngine APIsNode, Electron, a private HTTP server, DOM
Dedicated serverJARVIGServerCore, world, gameplay, networkingRenderer, editor, UI
Web exportWASM plus a small platform layerThe same engine APIA second world model written in JavaScript
CLI and build farmtoolsThe same engine API the editor usesA private copy of cook or import

The processes under apps/ and hosts/ today are Node prototypes of those hosts. apps/editor serves a temporary dock so the command bus can be tested. That page is not the product editor and it does not present. The product window is native/jarvig_editor (JARVIGEditor.exe). native/jarvig_editor_host is the two-view renderer test. apps/player/ is reserved for the native player and is empty on purpose. The editor executable is not that player.

winit stays inside jarvig_platform. The renderer never imports it.

@jarvig/node-host is allowed to use Node. engine/** is not.