@portalshq/resolver 0.0.2 → 0.0.4

package/dist/index.d.ts

@@ -0,0 +1 @@
+export * from "./nap-resolver-adapter.js";

package/dist/index.js

@@ -0,0 +1 @@
+export * from "./nap-resolver-adapter.js";

package/dist/nap-resolver-adapter.d.ts

@@ -0,0 +1,28 @@
+/**
+ * IMPORTANT: this does not reimplement NAP. It wraps the existing NAP v0
+ * client (already running in studio-app and 25thChapter) so that any
+ * capability in this repo can resolve a NAP address through one stable
+ * interface, without depending on the v0 client's internal API surface
+ * directly. If/when NAP moves past v0, only this adapter should need to
+ * change — not every capability that consumes it.
+ *
+ * TODO(integration): replace the placeholder import below with the actual
+ * NAP v0 client package once it's extracted from studio-app into its own
+ * package. Until then this adapter defines the target interface so other
+ * packages can be built against it in parallel.
+ */
+export interface NarrativeObject {
+    napAddress: string;
+    kind: "narrative" | "world" | "asset" | "identity";
+    lineage?: string[];
+    payload: unknown;
+}
+export interface NapResolver {
+    resolve(napAddress: string): Promise<NarrativeObject>;
+    exists(napAddress: string): Promise<boolean>;
+}
+export declare class NapResolverAdapter implements NapResolver {
+    constructor();
+    resolve(napAddress: string): Promise<NarrativeObject>;
+    exists(napAddress: string): Promise<boolean>;
+}

package/dist/nap-resolver-adapter.js

@@ -0,0 +1,23 @@
+/**
+ * IMPORTANT: this does not reimplement NAP. It wraps the existing NAP v0
+ * client (already running in studio-app and 25thChapter) so that any
+ * capability in this repo can resolve a NAP address through one stable
+ * interface, without depending on the v0 client's internal API surface
+ * directly. If/when NAP moves past v0, only this adapter should need to
+ * change — not every capability that consumes it.
+ *
+ * TODO(integration): replace the placeholder import below with the actual
+ * NAP v0 client package once it's extracted from studio-app into its own
+ * package. Until then this adapter defines the target interface so other
+ * packages can be built against it in parallel.
+ */
+export class NapResolverAdapter {
+    constructor( /* private client: NapClientV0 */) { }
+    async resolve(napAddress) {
+        // return this.client.resolve(napAddress);
+        throw new Error("NapResolverAdapter.resolve: wire up to NAP v0 client — see TODO above");
+    }
+    async exists(napAddress) {
+        throw new Error("NapResolverAdapter.exists: wire up to NAP v0 client — see TODO above");
+    }
+}

package/package.json

@@ -1,13 +1,31 @@
 {
   "name": "@portalshq/resolver",
-  "version": "0.0.2",
+  "version": "0.0.4",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/portalshq/portals-cloud"
+    "url": "git+https://github.com/portalshq/portals-cloud.git",
+    "directory": "packages/resolver"
   },
   "description": "Adapter over the existing NAP v0 client. Gives NAP a stable, contract-compliant interface consumable by any capability, not just studio-app/25thChapter's bespoke integrations.",
-  "main": "src/index.ts",
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "files": [
+    "dist"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "typecheck": "tsc -p tsconfig.json --noEmit"
+  },
   "dependencies": {
     "@portalshq/contracts": "*"
+  },
+  "devDependencies": {
+    "typescript": "^5.5.0",
+    "@types/node": "^20.0.0"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
   }
 }

package/src/index.ts

@@ -1 +0,0 @@
-export * from "./nap-resolver-adapter";

package/src/nap-resolver-adapter.ts

@@ -1,40 +0,0 @@
-/**
- * IMPORTANT: this does not reimplement NAP. It wraps the existing NAP v0
- * client (already running in studio-app and 25thChapter) so that any
- * capability in this repo can resolve a NAP address through one stable
- * interface, without depending on the v0 client's internal API surface
- * directly. If/when NAP moves past v0, only this adapter should need to
- * change — not every capability that consumes it.
- *
- * TODO(integration): replace the placeholder import below with the actual
- * NAP v0 client package once it's extracted from studio-app into its own
- * package. Until then this adapter defines the target interface so other
- * packages can be built against it in parallel.
- */
-
-// import { NapClientV0 } from "@portalshq/protocol-v0"; // <-- existing v0 client, once extracted
-
-export interface NarrativeObject {
-  napAddress: string;
-  kind: "narrative" | "world" | "asset" | "identity";
-  lineage?: string[];   // provenance chain — see docs ADR on remixing/attribution
-  payload: unknown;
-}
-
-export interface NapResolver {
-  resolve(napAddress: string): Promise<NarrativeObject>;
-  exists(napAddress: string): Promise<boolean>;
-}
-
-export class NapResolverAdapter implements NapResolver {
-  constructor(/* private client: NapClientV0 */) {}
-
-  async resolve(napAddress: string): Promise<NarrativeObject> {
-    // return this.client.resolve(napAddress);
-    throw new Error("NapResolverAdapter.resolve: wire up to NAP v0 client — see TODO above");
-  }
-
-  async exists(napAddress: string): Promise<boolean> {
-    throw new Error("NapResolverAdapter.exists: wire up to NAP v0 client — see TODO above");
-  }
-}