@ory/argus 0.1.0

package/dist/registry/main.d.ts

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+/**
+ * Standalone entry point for `registry` commands.
+ *
+ * Used by root package.json scripts: node packages/core/dist/registry/main.js <subcommand>
+ */
+export {};

package/dist/registry/main.js

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+"use strict";
+/**
+ * Standalone entry point for `registry` commands.
+ *
+ * Used by root package.json scripts: node packages/core/dist/registry/main.js <subcommand>
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+const cli_js_1 = require("./cli.js");
+const args = process.argv.slice(2);
+(0, cli_js_1.runRegistryCommand)("pnpm", args).catch((err) => {
+    console.error(err.message ?? err);
+    process.exit(1);
+});

package/dist/registry/manager.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Local npm registry manager.
+ *
+ * Manages a Verdaccio Docker container for publishing and installing
+ * @ory packages locally. Completely ephemeral — the
+ * container is started with `--rm` and all state lives under
+ * `.ory-dev/registry/` on the host, bind-mounted into the container.
+ *
+ * Mirrors the lifecycle model used by the standalone Jaeger container
+ * (see `local/jaeger.ts`): single `docker run -d --rm --name <name>`,
+ * idempotent start, removal via `docker rm -f`.
+ */
+/**
+ * Per-registry npm cache directory.
+ *
+ * Isolating npm's pacote cache here is the only way to keep republishing
+ * the same version reliably — npm caches manifests by URL, so the user's
+ * `~/.npm` would otherwise serve stale "this version exists" answers to
+ * pnpm publish/npm install even after we drop the version from Verdaccio.
+ */
+export declare function getLocalRegistryNpmCacheDir(): string;
+/**
+ * Start the local registry if it isn't already running.
+ */
+export declare function ensureRegistryRunning(): Promise<void>;
+/**
+ * Publish all `@ory/*` packages to the local registry — entrypoint used by
+ * the dev launcher. The `harnessName` arg is retained for call-site
+ * compatibility; we publish the whole scope every time so any harness gets
+ * a coherent registry state without needing to compute its dep closure.
+ */
+export declare function publishHarnessToLocal(_harnessName: string): Promise<void>;
+export declare function registryStart(): Promise<void>;
+export declare function registryStop(): Promise<void>;
+export declare function registryStatus(): Promise<void>;
+export declare function registryPublish(): Promise<void>;
+export declare function registryClean(): Promise<void>;
+export declare function registryNpmrc(): Promise<void>;