Skip to main content

Module types

Module types 

Source

Modules§

credentials
Credentials type definitions for CLI authentication
project
Project configuration types

Structs§

Credentials
DeviceCodeResponse
EnvironmentConfig
Configuration for a specific environment
EnvironmentsConfig
Per-environment configuration (dev, staging, prod), with the active environment selected via the MECHA10_ENV environment variable or --env flag.
NodeSpec
Parsed node specification from namespaced string format
NodesConfig
Map of node identifiers (e.g. @mecha10/listener, my-custom) to their pinned versions.
ProjectConfig
TurnConfig
Resolved TURN server config: relay URL + credentials for a TURN entry in a WebRTC ICE server list. Kept as a standalone type here (rather than reusing mecha10_video::webrtc::connection::TurnServerConfig) since mecha10-cli-core intentionally doesn’t depend on mecha10-video - mecha10-video and the nodes that embed it (camera, video-streamer) are meant to stay lightweight for robot binaries, the same “minimal dependencies” rationale mecha10-node-resolver documents for inlining its own copy of DEFAULT_MECHA10_API_URL instead of depending on this crate.

Enums§

AuthError
DeviceCodeStatus
NodeSource
Node source type based on namespace prefix

Functions§

is_local_project_node
Whether name is declared as a local project node (NodeSource::Project, i.e. built from this project’s own nodes/<name> workspace member) according to the mecha10.json at config_path - the single shared check behind both mecha10 dev’s ProcessService::spawn_node_direct and mecha10-node-runner’s resolve_node_execution, so the two don’t drift onto different classification rules for the same node.
load_project_config
Load full project config from mecha10.json
turn_config
Resolve TURN server config, highest priority first: