@le-space/ui 0.6.46 → 0.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@le-space/ui",
-  "version": "0.6.46",
+  "version": "0.8.0",
   "description": "Floating Aleph Relay Button UI components for Svelte and React.",
   "license": "MIT",
   "type": "module",
@@ -44,8 +44,8 @@
     "url": "https://github.com/NiKrause/relay-button/issues"
   },
   "dependencies": {
-    "@le-space/browser": "0.6.46",
-    "@le-space/core": "0.6.46",
+    "@le-space/browser": "0.8.0",
+    "@le-space/core": "0.8.0",
     "viem": "^2.53.1"
   },
   "peerDependencies": {

package/react/index.d.ts

@@ -255,6 +255,12 @@ interface CompactInstanceDetails {
     vmIpv4: string | null;
     webUrl: string | null;
     sshCommand: string | null;
+    /**
+     * Hostname of the deployment's HTTPS proxy. The mapped ports are plain HTTP,
+     * which a browser on an HTTPS page refuses to fetch, so this is the only
+     * address the card can read the relay's own documents from.
+     */
+    proxyHostname: string | null;
     mappedPorts: Array<{
         label: string;
         hostPort: number | null;
@@ -262,6 +268,32 @@ interface CompactInstanceDetails {
     execution: InstanceExecution | null;
     error: string | null;
 }
+/** One transport's worth of addresses, as the relay itself groups them. */
+interface SponsorRelayAddressGroup {
+    key: string;
+    label: string;
+    addresses: string[];
+}
+/**
+ * What a deployment reports about itself at `/multiaddrs`. Deliberately not
+ * normalised into "the best address": the card shows what the relay says, and
+ * choosing between addresses is the consumer's business, not this UI's.
+ */
+interface SponsorRelayInstanceAddresses {
+    status: 'idle' | 'loading' | 'ready' | 'unsupported' | 'error';
+    /** Transport groups, empty for a profile that publishes no libp2p addresses. */
+    groups: SponsorRelayAddressGroup[];
+    /** Ready-to-paste environment block, when the profile publishes one. */
+    pwaEnv: Record<string, string> | null;
+    /** Raw payload, rendered verbatim on the health tab. */
+    payload: Record<string, unknown> | null;
+    peerId: string | null;
+    version: string | null;
+    fetchedAt: number | null;
+    error: string | null;
+    /** Source URL, shown so a person can curl exactly what the card read. */
+    sourceUrl: string | null;
+}
 interface CompactInstanceRecord {
     instance: InstanceMessage;
     details: CompactInstanceDetails;
@@ -326,6 +358,13 @@ interface SponsorRelayState {
     orphanBootstrapRegistrations: CompactBootstrapRegistrationRecord[];
     lastDeploymentHash: string | null;
     deploymentProgress: DeploymentProgressEvent;
+    /**
+     * What each deployment reports at `/multiaddrs`, keyed by instance item hash.
+     * Fetched on demand rather than with the instance list: AutoTLS addresses only
+     * appear a minute or two after a deploy reports success, so this is state that
+     * has to be refreshable on its own.
+     */
+    instanceAddresses: Record<string, SponsorRelayInstanceAddresses>;
 }
 type SponsorRelaySubscriber = (state: SponsorRelayState) => void;
 
@@ -379,6 +418,18 @@ declare class SponsorRelayController {
     private refreshWalletDerivedState;
     refresh(): Promise<void>;
     deploy(): Promise<void>;
+    /**
+     * Read one deployment's own address document over its HTTPS proxy.
+     *
+     * The mapped ports are plain HTTP, which a browser on an HTTPS page refuses to
+     * fetch, so the proxy hostname is the only way in. Deliberately single-shot:
+     * unlike the deploy-time readiness probe this backs a button someone pressed,
+     * and a caller who wants newer data presses it again.
+     */
+    loadInstanceAddresses(instanceHash: string, options?: {
+        force?: boolean;
+    }): Promise<void>;
+    private patchInstanceAddresses;
     deleteInstance(instanceHash: string): Promise<void>;
     deleteBootstrapRegistration(registrationHash: string): Promise<void>;
 }