vite-plugin-io1 0.1.0 → 0.1.1

package/README.md

@@ -10,11 +10,15 @@ startup output.
 
 ## Why
 
-- **Real HTTPS, real cert** so secure-context APIs (service workers, camera, WebCrypto) just work.
-- **Working HMR through the tunnel** -- the shared URL is your live dev server, not a static copy.
-- **Email-gated sharing** via `allowedEmails` makes a preview shared-but-not-public.
-- **No `server.allowedHosts` fuss** -- the relay presents the upstream's own Host, so Vite's host
-  check never trips.
+A tunnel is only worth anything if it points at the dev server you are actually editing, and this
+one does: the public URL is your running `vite dev` - HMR and all - so a teammate (or your phone)
+hits the same live server you have open, and a save reloads their page in place. It arrives over a
+genuine HTTPS cert, so the secure-context APIs that quietly refuse to run on plain HTTP - service
+workers, the camera, WebCrypto - just work.
+
+Set `allowedEmails` and the preview turns shared-but-not-public: a visitor verifies one of those
+addresses before the host resolves for them. And because the relay presents the upstream's own Host,
+Vite's host check never trips - there is no `server.allowedHosts` to wrangle.
 
 ## Install
 
@@ -71,14 +75,14 @@ explicitly for a shared demo host.
 
 The `bitmot` CLI carries a version (`bitmot version`), and the gateway advertises the latest one on
 every relay handshake; run by hand, the CLI nudges you when you are out of date. That nudge is
-deliberately silent when its output is piped or `CI` is set -- that is, whenever this plugin runs it.
+deliberately silent when its output is piped or `CI` is set - that is, whenever this plugin runs it.
 So the plugin keeps the CLI current a different way: auto-download resolves the **currently deployed**
 bytes by content hash, so a plugin-managed CLI is always up to date and the nudge is moot. A CLI you
 installed yourself on your PATH is respected as-is and never replaced.
 
 ## Caveats
 
-- **macOS and Linux** -- published binaries cover macOS (arm64/x86_64) and Linux (x86_64/aarch64).
+- **macOS and Linux** - published binaries cover macOS (arm64/x86_64) and Linux (x86_64/aarch64).
   Elsewhere (e.g. native Windows), install `bitmot` yourself (the plugin will use it) or set
   `bitmotPath`.
 - **Middleware mode** (e.g. Nuxt) exposes no `httpServer` for the plugin to hook; not yet supported.

package/dist/announce.d.ts

@@ -1,6 +1,6 @@
 /**
  * Pure argument-building and output-parsing for the bitmot io1 relay. Kept free of I/O so the wire
- * contract with the CLI -- which flags it takes, and how it announces a live host -- is unit-tested
+ * contract with the CLI - which flags it takes, and how it announces a live host - is unit-tested
  * in isolation and lives in one place.
  */
 export interface RelayInvocation {
@@ -30,7 +30,7 @@ export declare function buildRelayArgs(invocation: RelayInvocation): string[];
  * The public URL from a relay's per-host announcement line, or null for any other line. The relay
  * prints one `<arrow> <url> live` line per claimed host once its link is up (uncolored when its
  * stderr is piped, as it is under this plugin). Tolerant of the arrow glyph and surrounding spaces so
- * both the native and JVM CLIs -- and any cached older build -- parse the same; the trailing `live`
+ * both the native and JVM CLIs - and any cached older build - parse the same; the trailing `live`
  * badge is what distinguishes it from the pending-requests and update-nudge lines, which also carry
  * URLs but must not be mistaken for a live host.
  */

package/dist/announce.js

@@ -1,6 +1,6 @@
 /**
  * Pure argument-building and output-parsing for the bitmot io1 relay. Kept free of I/O so the wire
- * contract with the CLI -- which flags it takes, and how it announces a live host -- is unit-tested
+ * contract with the CLI - which flags it takes, and how it announces a live host - is unit-tested
  * in isolation and lives in one place.
  */
 /**
@@ -31,7 +31,7 @@ export function buildRelayArgs(invocation) {
  * The public URL from a relay's per-host announcement line, or null for any other line. The relay
  * prints one `<arrow> <url> live` line per claimed host once its link is up (uncolored when its
  * stderr is piped, as it is under this plugin). Tolerant of the arrow glyph and surrounding spaces so
- * both the native and JVM CLIs -- and any cached older build -- parse the same; the trailing `live`
+ * both the native and JVM CLIs - and any cached older build - parse the same; the trailing `live`
  * badge is what distinguishes it from the pending-requests and update-nudge lines, which also carry
  * URLs but must not be mistaken for a live host.
  */

package/dist/binary.d.ts

@@ -22,7 +22,7 @@ export interface ResolvedBinary {
  * The published artifact name for a platform/arch, or null when unsupported. Mirrors the server's
  * download whitelist (io/io1/gateway/download/DownloadRoutesImpl.kt) and the installer's `uname`
  * mapping: macOS and Linux, on x86_64 or 64-bit ARM. Node's arch is translated to the server's
- * spelling -- 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
+ * spelling - 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
  */
 export declare function artifactFor(platform: NodeJS.Platform, arch: string): string | null;
 /** `bitmot version` -> "0.2.1", or null if the binary is missing or its output is unexpected. */
@@ -33,7 +33,7 @@ export declare function readVersion(binary: string): string | null;
  * followed response's checksum header names the current version: if a file for that hash is already
  * cached the body is dropped undownloaded, otherwise it is streamed, verified against the advertised
  * checksum, and atomically installed. This is what makes a plugin-managed CLI track production
- * automatically -- so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
+ * automatically - so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
  * piped, as it is here) does not matter for the auto-managed case.
  */
 export declare function ensureDownloaded(baseUrl: string, artifact: string, cacheDir: string, log?: (message: string) => void): Promise<{

package/dist/binary.js

@@ -11,7 +11,7 @@ const DEFAULT_BASE_URL = 'https://bitmot.com';
  * The published artifact name for a platform/arch, or null when unsupported. Mirrors the server's
  * download whitelist (io/io1/gateway/download/DownloadRoutesImpl.kt) and the installer's `uname`
  * mapping: macOS and Linux, on x86_64 or 64-bit ARM. Node's arch is translated to the server's
- * spelling -- 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
+ * spelling - 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
  */
 export function artifactFor(platform, arch) {
     if (platform === 'darwin') {
@@ -63,7 +63,7 @@ function onPath() {
  * followed response's checksum header names the current version: if a file for that hash is already
  * cached the body is dropped undownloaded, otherwise it is streamed, verified against the advertised
  * checksum, and atomically installed. This is what makes a plugin-managed CLI track production
- * automatically -- so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
+ * automatically - so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
  * piped, as it is here) does not matter for the auto-managed case.
  */
 export async function ensureDownloaded(baseUrl, artifact, cacheDir, log) {

package/dist/index.d.ts

@@ -28,7 +28,7 @@ export interface Io1PluginOptions {
 /**
  * Vite plugin: while the dev (or preview) server runs, publish it to the internet over a
  * `bitmot io1 relay` child process, proxying to the server's real bound port. The relay's lifetime is
- * tied to the server -- spawned once it is listening, killed when it closes -- so a shared URL never
+ * tied to the server - spawned once it is listening, killed when it closes - so a shared URL never
  * outlives the session. The CLI is located on PATH or auto-downloaded (content-addressed, so it tracks
  * the deployed build). Reconnects are the relay's own concern; a non-zero exit is a definitive refusal
  * (bad auth, host held by another account) and is surfaced, not retried.

package/dist/index.js

@@ -10,7 +10,7 @@ function normalizeHosts(host) {
 /**
  * Vite plugin: while the dev (or preview) server runs, publish it to the internet over a
  * `bitmot io1 relay` child process, proxying to the server's real bound port. The relay's lifetime is
- * tied to the server -- spawned once it is listening, killed when it closes -- so a shared URL never
+ * tied to the server - spawned once it is listening, killed when it closes - so a shared URL never
  * outlives the session. The CLI is located on PATH or auto-downloaded (content-addressed, so it tracks
  * the deployed build). Reconnects are the relay's own concern; a non-zero exit is a definitive refusal
  * (bad auth, host held by another account) and is surfaced, not retried.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plugin-io1",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Publish your Vite dev server to the public internet over a bitmot io1 relay, with the CLI auto-managed.",
   "keywords": [
     "vite",

package/src/announce.ts

@@ -1,6 +1,6 @@
 /**
  * Pure argument-building and output-parsing for the bitmot io1 relay. Kept free of I/O so the wire
- * contract with the CLI -- which flags it takes, and how it announces a live host -- is unit-tested
+ * contract with the CLI - which flags it takes, and how it announces a live host - is unit-tested
  * in isolation and lives in one place.
  */
 
@@ -44,7 +44,7 @@ export function buildRelayArgs(invocation: RelayInvocation): string[] {
  * The public URL from a relay's per-host announcement line, or null for any other line. The relay
  * prints one `<arrow> <url> live` line per claimed host once its link is up (uncolored when its
  * stderr is piped, as it is under this plugin). Tolerant of the arrow glyph and surrounding spaces so
- * both the native and JVM CLIs -- and any cached older build -- parse the same; the trailing `live`
+ * both the native and JVM CLIs - and any cached older build - parse the same; the trailing `live`
  * badge is what distinguishes it from the pending-requests and update-nudge lines, which also carry
  * URLs but must not be mistaken for a live host.
  */

package/src/binary.ts

@@ -36,7 +36,7 @@ const DEFAULT_BASE_URL = 'https://bitmot.com'
  * The published artifact name for a platform/arch, or null when unsupported. Mirrors the server's
  * download whitelist (io/io1/gateway/download/DownloadRoutesImpl.kt) and the installer's `uname`
  * mapping: macOS and Linux, on x86_64 or 64-bit ARM. Node's arch is translated to the server's
- * spelling -- 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
+ * spelling - 'x64' -> 'x86_64' on both, but 64-bit ARM is 'arm64' on macOS and 'aarch64' on Linux.
  */
 export function artifactFor(platform: NodeJS.Platform, arch: string): string | null {
   if (platform === 'darwin') {
@@ -87,7 +87,7 @@ function onPath(): boolean {
  * followed response's checksum header names the current version: if a file for that hash is already
  * cached the body is dropped undownloaded, otherwise it is streamed, verified against the advertised
  * checksum, and atomically installed. This is what makes a plugin-managed CLI track production
- * automatically -- so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
+ * automatically - so the CLI's own "you're out of date" nudge (suppressed anyway when its stderr is
  * piped, as it is here) does not matter for the auto-managed case.
  */
 export async function ensureDownloaded(

package/src/index.ts

@@ -42,7 +42,7 @@ type ServeServer = ViteDevServer | PreviewServer
 /**
  * Vite plugin: while the dev (or preview) server runs, publish it to the internet over a
  * `bitmot io1 relay` child process, proxying to the server's real bound port. The relay's lifetime is
- * tied to the server -- spawned once it is listening, killed when it closes -- so a shared URL never
+ * tied to the server - spawned once it is listening, killed when it closes - so a shared URL never
  * outlives the session. The CLI is located on PATH or auto-downloaded (content-addressed, so it tracks
  * the deployed build). Reconnects are the relay's own concern; a non-zero exit is a definitive refusal
  * (bad auth, host held by another account) and is surfaced, not retried.