EXPO-RUNTIME

Declarative runtime integration for Expo apps: maps app capabilities to permissions, packages, config plugins, providers, and adapters

Usage

CLI

Ankhorage packages expose their command-line interface through ankh. Use ankh --help to discover available package commands, or run a package command with --help for package-specific usage.

# Install the Ankhorage CLI
bun add --global @ankhorage/ankh

# Show usage information for expo-runtime
ankh expo-runtime --help

Basic Usage

Derive the Expo packages, providers, config plugins, and runtime adapters required by an app directly from its declared screen requirements. The planner keeps Expo-specific implementation details out of the manifest while preserving one deterministic owner-derived runtime plan.

This example requests barcode scanning on one screen. Expo Runtime automatically includes the implied camera permission, Expo Camera dependency, permissions provider, and barcode adapter.

export function createBasicExpoRuntimePlan() {
  return resolveExpoRuntimePlan({
    screens: {
      scanner: {
        requires: {
          capabilities: {
            barcodeScanner: true,
          },
        },
      },
    },
  });
}

Generated documentation

• Interactive documentation app
• Public API reference
• Component registry
• Architecture overview
• Module relationships
• Export graph
• createExpoRuntimeRegistry sequence
• ExpoBarcodeScannerAdapter sequence
• ExpoZoraIconFontProvider sequence
• getExpoBundledMediaRegistrySource sequence
• resolveExpoRuntimeGeneratedAppOutput sequence
• resolveExpoRuntimeNativeOutput sequence