@lumeweb/pinner 0.1.1 → 0.1.4

package/dist/esm/api/generated/schemas/iPNSKeyRequest.d.ts

@@ -0,0 +1,43 @@
+//#region src/api/generated/schemas/iPNSKeyRequest.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface IPNSKeyRequest {
+  key?: string;
+  name: string;
+}
+//#endregion
+export { IPNSKeyRequest };
+//# sourceMappingURL=iPNSKeyRequest.d.ts.map

package/dist/esm/api/generated/schemas/iPNSKeyResponse.d.ts

@@ -0,0 +1,46 @@
+//#region src/api/generated/schemas/iPNSKeyResponse.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface IPNSKeyResponse {
+  created: string;
+  id: number;
+  ipns_name: string;
+  name: string;
+  peer_id: string;
+}
+//#endregion
+export { IPNSKeyResponse };
+//# sourceMappingURL=iPNSKeyResponse.d.ts.map

package/dist/esm/api/generated/schemas/iPNSPublishRequest.d.ts

@@ -0,0 +1,44 @@
+//#region src/api/generated/schemas/iPNSPublishRequest.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface IPNSPublishRequest {
+  cid: string;
+  key_id: number;
+  ttl?: string;
+}
+//#endregion
+export { IPNSPublishRequest };
+//# sourceMappingURL=iPNSPublishRequest.d.ts.map

package/dist/esm/api/generated/schemas/iPNSPublishResponse.d.ts

@@ -0,0 +1,46 @@
+//#region src/api/generated/schemas/iPNSPublishResponse.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface IPNSPublishResponse {
+  name: string;
+  published: string;
+  sequence: number;
+  validity: string;
+  value: string;
+}
+//#endregion
+export { IPNSPublishResponse };
+//# sourceMappingURL=iPNSPublishResponse.d.ts.map

package/dist/esm/api/generated/schemas/iPNSResolveResponse.d.ts

@@ -0,0 +1,47 @@
+//#region src/api/generated/schemas/iPNSResolveResponse.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface IPNSResolveResponse {
+  expired: boolean;
+  expires: string;
+  name: string;
+  path: string;
+  sequence: number;
+  value: string;
+}
+//#endregion
+export { IPNSResolveResponse };
+//# sourceMappingURL=iPNSResolveResponse.d.ts.map

package/dist/esm/api/generated/schemas/sSLStatusInfo.d.ts

@@ -0,0 +1,45 @@
+//#region src/api/generated/schemas/sSLStatusInfo.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface SSLStatusInfo {
+  error?: string;
+  issued_at?: string;
+  last_updated_at?: string;
+  status: string;
+}
+//#endregion
+export { SSLStatusInfo };
+//# sourceMappingURL=sSLStatusInfo.d.ts.map

package/dist/esm/api/generated/schemas/websiteConfigResponse.d.ts

@@ -0,0 +1,43 @@
+//#region src/api/generated/schemas/websiteConfigResponse.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface WebsiteConfigResponse {
+  gateway_domain?: string;
+  nameservers?: string[];
+}
+//#endregion
+export { WebsiteConfigResponse };
+//# sourceMappingURL=websiteConfigResponse.d.ts.map

package/dist/esm/api/generated/schemas/websiteItem.d.ts

@@ -0,0 +1,23 @@
+import { SSLStatusInfo } from "./sSLStatusInfo.js";
+
+//#region src/api/generated/schemas/websiteItem.d.ts
+interface WebsiteItem {
+  created: string;
+  dns_hosting_enabled: boolean;
+  dns_zone_id?: number;
+  domain: string;
+  expired: boolean;
+  gateway_domain?: string;
+  id: number;
+  last_checked_at?: string;
+  ssl?: SSLStatusInfo;
+  status: string;
+  target_hash: string;
+  target_type: string;
+  updated: string;
+  validation_expires_at?: string;
+  validation_token: string;
+}
+//#endregion
+export { WebsiteItem };
+//# sourceMappingURL=websiteItem.d.ts.map

package/dist/esm/api/generated/schemas/websiteItemResponse.d.ts

@@ -0,0 +1,10 @@
+import { WebsiteItem } from "./websiteItem.js";
+
+//#region src/api/generated/schemas/websiteItemResponse.d.ts
+interface WebsiteItemResponse {
+  data: WebsiteItem[];
+  total: number;
+}
+//#endregion
+export { WebsiteItemResponse };
+//# sourceMappingURL=websiteItemResponse.d.ts.map

package/dist/esm/api/generated/schemas/websiteRequest.d.ts

@@ -0,0 +1,45 @@
+//#region src/api/generated/schemas/websiteRequest.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface WebsiteRequest {
+  dns_hosting_enabled?: boolean;
+  domain: string;
+  target_hash: string;
+  target_type: string;
+}
+//#endregion
+export { WebsiteRequest };
+//# sourceMappingURL=websiteRequest.d.ts.map

package/dist/esm/api/generated/schemas/websiteResponse.d.ts

@@ -0,0 +1,23 @@
+import { SSLStatusInfo } from "./sSLStatusInfo.js";
+
+//#region src/api/generated/schemas/websiteResponse.d.ts
+interface WebsiteResponse {
+  created: string;
+  dns_hosting_enabled: boolean;
+  dns_zone_id?: number;
+  domain: string;
+  expired: boolean;
+  gateway_domain?: string;
+  id: number;
+  last_checked_at?: string;
+  ssl?: SSLStatusInfo;
+  status: string;
+  target_hash: string;
+  target_type: string;
+  updated: string;
+  validation_expires_at?: string;
+  validation_token: string;
+}
+//#endregion
+export { WebsiteResponse };
+//# sourceMappingURL=websiteResponse.d.ts.map

package/dist/esm/api/generated/schemas/websiteUpdateRequest.d.ts

@@ -0,0 +1,45 @@
+//#region src/api/generated/schemas/websiteUpdateRequest.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface WebsiteUpdateRequest {
+  dns_hosting_enabled?: boolean;
+  domain?: string;
+  target_hash?: string;
+  target_type?: string;
+}
+//#endregion
+export { WebsiteUpdateRequest };
+//# sourceMappingURL=websiteUpdateRequest.d.ts.map

package/dist/esm/api/generated/schemas/websiteValidateResponse.d.ts

@@ -0,0 +1,45 @@
+//#region src/api/generated/schemas/websiteValidateResponse.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Portal IPFS Plugin API
+ *
+## Portal IPFS Plugin API
+
+A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+
+### IPFS Pinning Service API Compatibility
+
+This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+
+### Features
+
+- **Pinning**: Add, list, update, and remove pinned content
+- **Content**: Upload files, retrieve IPFS content, and manage metadata
+- **IPNS**: Manage IPNS keys and publish content
+- **Files**: Browse and manage pinned files with directory navigation
+- **Websites**: Create and manage website hosting with DNS and SSL automation
+
+### Authentication
+
+All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+
+### Rate Limiting
+
+API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+
+### Documentation
+
+For detailed API usage examples and integration guides, visit the Portal documentation website.
+
+ * OpenAPI spec version: 1.0.0
+ */
+interface WebsiteValidateResponse {
+  domain: string;
+  id: number;
+  message: string;
+  valid: boolean;
+}
+//#endregion
+export { WebsiteValidateResponse };
+//# sourceMappingURL=websiteValidateResponse.d.ts.map

package/dist/esm/api/ipns.d.ts

@@ -0,0 +1,28 @@
+import { PinnerConfig } from "../config.js";
+import { IPNSKeyListResponseResponse } from "./generated/schemas/iPNSKeyListResponseResponse.js";
+import { IPNSKeyRequest } from "./generated/schemas/iPNSKeyRequest.js";
+import { IPNSKeyResponse } from "./generated/schemas/iPNSKeyResponse.js";
+import { IPNSPublishRequest } from "./generated/schemas/iPNSPublishRequest.js";
+import { IPNSPublishResponse } from "./generated/schemas/iPNSPublishResponse.js";
+import { IPNSResolveResponse } from "./generated/schemas/iPNSResolveResponse.js";
+
+//#region src/api/ipns.d.ts
+interface IpnsClientOptions {
+  signal?: AbortSignal;
+}
+declare class IpnsClient {
+  private config;
+  constructor(config: PinnerConfig);
+  private getEndpoint;
+  private request;
+  listKeys(options?: IpnsClientOptions): Promise<IPNSKeyListResponseResponse>;
+  getKey(id: number, options?: IpnsClientOptions): Promise<IPNSKeyResponse>;
+  createKey(request: IPNSKeyRequest, options?: IpnsClientOptions): Promise<IPNSKeyResponse>;
+  deleteKey(id: number, options?: IpnsClientOptions): Promise<void>;
+  publish(request: IPNSPublishRequest, options?: IpnsClientOptions): Promise<IPNSPublishResponse>;
+  republish(name: string, options?: IpnsClientOptions): Promise<void>;
+  resolve(name: string, options?: IpnsClientOptions): Promise<IPNSResolveResponse>;
+}
+//#endregion
+export { IpnsClient };
+//# sourceMappingURL=ipns.d.ts.map

package/dist/esm/api/ipns.js

@@ -0,0 +1,83 @@
+import { AuthenticationError, ConfigurationError, NetworkError, NotFoundError, ValidationError } from "../errors/index.js";
+import ky, { HTTPError } from "ky";
+
+//#region src/api/ipns.ts
+var IpnsClient = class {
+	config;
+	constructor(config) {
+		if (!config.jwt) throw new ConfigurationError("JWT token is required");
+		this.config = config;
+	}
+	getEndpoint() {
+		return this.config.endpoint ?? "https://ipfs.pinner.xyz";
+	}
+	async request(path, options) {
+		if (!this.config.jwt) throw new ConfigurationError("JWT token is required");
+		try {
+			const response = await ky(path, {
+				prefix: this.getEndpoint(),
+				headers: {
+					Authorization: `Bearer ${this.config.jwt}`,
+					"Content-Type": "application/json"
+				},
+				...options
+			});
+			if (response.status === 204) return;
+			const text = await response.text();
+			if (!text) return;
+			return JSON.parse(text);
+		} catch (error) {
+			if (error instanceof HTTPError) {
+				const status = error.response.status;
+				const body = await error.response.json().catch(() => ({}));
+				if (status === 401) throw new AuthenticationError(body.error || "Authentication failed");
+				if (status === 403) throw new AuthenticationError(body.error || "Access forbidden");
+				if (status === 404) throw new NotFoundError(body.error || "Resource not found");
+				if (status === 400) throw new ValidationError(body.error || "Invalid request");
+				throw new NetworkError(body.error || `HTTP error: ${status}`, status);
+			}
+			if (error instanceof Error) throw new NetworkError(error.message);
+			throw new NetworkError("Unknown error occurred");
+		}
+	}
+	async listKeys(options) {
+		return this.request("api/ipns/keys", { signal: options?.signal });
+	}
+	async getKey(id, options) {
+		return this.request(`api/ipns/keys/${id}`, { signal: options?.signal });
+	}
+	async createKey(request, options) {
+		return this.request("api/ipns/keys", {
+			method: "POST",
+			body: JSON.stringify(request),
+			signal: options?.signal
+		});
+	}
+	async deleteKey(id, options) {
+		await this.request(`api/ipns/keys/${id}`, {
+			method: "DELETE",
+			signal: options?.signal
+		});
+	}
+	async publish(request, options) {
+		return this.request("api/ipns/publish", {
+			method: "POST",
+			body: JSON.stringify(request),
+			signal: options?.signal
+		});
+	}
+	async republish(name, options) {
+		await this.request("api/ipns/republish", {
+			method: "POST",
+			body: JSON.stringify({ name }),
+			signal: options?.signal
+		});
+	}
+	async resolve(name, options) {
+		return this.request(`api/ipns/resolve/${name}`, { signal: options?.signal });
+	}
+};
+
+//#endregion
+export { IpnsClient };
+//# sourceMappingURL=ipns.js.map

package/dist/esm/api/ipns.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ipns.js","names":[],"sources":["../../../src/api/ipns.ts"],"sourcesContent":["import ky, { HTTPError } from \"ky\";\nimport type { PinnerConfig } from \"../config\";\nimport type {\n  IPNSKeyListResponseResponse,\n  IPNSKeyRequest,\n  IPNSKeyResponse,\n  IPNSPublishRequest,\n  IPNSPublishResponse,\n  IPNSResolveResponse,\n} from \"./generated/schemas/index\";\nimport {\n  ConfigurationError,\n  AuthenticationError,\n  NotFoundError,\n  NetworkError,\n  ValidationError,\n} from \"@/errors\";\n\nexport interface IpnsClientOptions {\n  signal?: AbortSignal;\n}\n\nexport class IpnsClient {\n  private config: PinnerConfig;\n\n  constructor(config: PinnerConfig) {\n    if (!config.jwt) {\n      throw new ConfigurationError(\"JWT token is required\");\n    }\n    this.config = config;\n  }\n\n  private getEndpoint(): string {\n    return this.config.endpoint ?? \"https://ipfs.pinner.xyz\";\n  }\n\n  private async request<T>(\n    path: string,\n    options?: RequestInit & { signal?: AbortSignal },\n  ): Promise<T> {\n    if (!this.config.jwt) {\n      throw new ConfigurationError(\"JWT token is required\");\n    }\n\n    try {\n      const response = await ky(path, {\n        prefix: this.getEndpoint(),\n        headers: {\n          Authorization: `Bearer ${this.config.jwt}`,\n          \"Content-Type\": \"application/json\",\n        },\n        ...options,\n      });\n\n      if (response.status === 204) {\n        return undefined as T;\n      }\n\n      const text = await response.text();\n      if (!text) {\n        return undefined as T;\n      }\n\n      return JSON.parse(text) as T;\n    } catch (error) {\n      if (error instanceof HTTPError) {\n        const status = error.response.status;\n        const body = await error.response.json().catch(() => ({}));\n\n        if (status === 401) {\n          throw new AuthenticationError(\n            body.error || \"Authentication failed\",\n          );\n        }\n        if (status === 403) {\n          throw new AuthenticationError(\n            body.error || \"Access forbidden\",\n          );\n        }\n        if (status === 404) {\n          throw new NotFoundError(body.error || \"Resource not found\");\n        }\n        if (status === 400) {\n          throw new ValidationError(body.error || \"Invalid request\");\n        }\n\n        throw new NetworkError(\n          body.error || `HTTP error: ${status}`,\n          status,\n        );\n      }\n\n      if (error instanceof Error) {\n        throw new NetworkError(error.message);\n      }\n\n      throw new NetworkError(\"Unknown error occurred\");\n    }\n  }\n\n  async listKeys(options?: IpnsClientOptions): Promise<IPNSKeyListResponseResponse> {\n    return this.request<IPNSKeyListResponseResponse>(\"api/ipns/keys\", {\n      signal: options?.signal,\n    });\n  }\n\n  async getKey(id: number, options?: IpnsClientOptions): Promise<IPNSKeyResponse> {\n    return this.request<IPNSKeyResponse>(`api/ipns/keys/${id}`, {\n      signal: options?.signal,\n    });\n  }\n\n  async createKey(\n    request: IPNSKeyRequest,\n    options?: IpnsClientOptions,\n  ): Promise<IPNSKeyResponse> {\n    return this.request<IPNSKeyResponse>(\"api/ipns/keys\", {\n      method: \"POST\",\n      body: JSON.stringify(request),\n      signal: options?.signal,\n    });\n  }\n\n  async deleteKey(id: number, options?: IpnsClientOptions): Promise<void> {\n    await this.request<void>(`api/ipns/keys/${id}`, {\n      method: \"DELETE\",\n      signal: options?.signal,\n    });\n  }\n\n  async publish(\n    request: IPNSPublishRequest,\n    options?: IpnsClientOptions,\n  ): Promise<IPNSPublishResponse> {\n    return this.request<IPNSPublishResponse>(\"api/ipns/publish\", {\n      method: \"POST\",\n      body: JSON.stringify(request),\n      signal: options?.signal,\n    });\n  }\n\n  async republish(\n    name: string,\n    options?: IpnsClientOptions,\n  ): Promise<void> {\n    await this.request<void>(\"api/ipns/republish\", {\n      method: \"POST\",\n      body: JSON.stringify({ name }),\n      signal: options?.signal,\n    });\n  }\n\n  async resolve(\n    name: string,\n    options?: IpnsClientOptions,\n  ): Promise<IPNSResolveResponse> {\n    return this.request<IPNSResolveResponse>(`api/ipns/resolve/${name}`, {\n      signal: options?.signal,\n    });\n  }\n}\n"],"mappings":";;;;AAsBA,IAAa,aAAb,MAAwB;CACtB,AAAQ;CAER,YAAY,QAAsB;AAChC,MAAI,CAAC,OAAO,IACV,OAAM,IAAI,mBAAmB,wBAAwB;AAEvD,OAAK,SAAS;;CAGhB,AAAQ,cAAsB;AAC5B,SAAO,KAAK,OAAO,YAAY;;CAGjC,MAAc,QACZ,MACA,SACY;AACZ,MAAI,CAAC,KAAK,OAAO,IACf,OAAM,IAAI,mBAAmB,wBAAwB;AAGvD,MAAI;GACF,MAAM,WAAW,MAAM,GAAG,MAAM;IAC9B,QAAQ,KAAK,aAAa;IAC1B,SAAS;KACP,eAAe,UAAU,KAAK,OAAO;KACrC,gBAAgB;KACjB;IACD,GAAG;IACJ,CAAC;AAEF,OAAI,SAAS,WAAW,IACtB;GAGF,MAAM,OAAO,MAAM,SAAS,MAAM;AAClC,OAAI,CAAC,KACH;AAGF,UAAO,KAAK,MAAM,KAAK;WAChB,OAAO;AACd,OAAI,iBAAiB,WAAW;IAC9B,MAAM,SAAS,MAAM,SAAS;IAC9B,MAAM,OAAO,MAAM,MAAM,SAAS,MAAM,CAAC,aAAa,EAAE,EAAE;AAE1D,QAAI,WAAW,IACb,OAAM,IAAI,oBACR,KAAK,SAAS,wBACf;AAEH,QAAI,WAAW,IACb,OAAM,IAAI,oBACR,KAAK,SAAS,mBACf;AAEH,QAAI,WAAW,IACb,OAAM,IAAI,cAAc,KAAK,SAAS,qBAAqB;AAE7D,QAAI,WAAW,IACb,OAAM,IAAI,gBAAgB,KAAK,SAAS,kBAAkB;AAG5D,UAAM,IAAI,aACR,KAAK,SAAS,eAAe,UAC7B,OACD;;AAGH,OAAI,iBAAiB,MACnB,OAAM,IAAI,aAAa,MAAM,QAAQ;AAGvC,SAAM,IAAI,aAAa,yBAAyB;;;CAIpD,MAAM,SAAS,SAAmE;AAChF,SAAO,KAAK,QAAqC,iBAAiB,EAChE,QAAQ,SAAS,QAClB,CAAC;;CAGJ,MAAM,OAAO,IAAY,SAAuD;AAC9E,SAAO,KAAK,QAAyB,iBAAiB,MAAM,EAC1D,QAAQ,SAAS,QAClB,CAAC;;CAGJ,MAAM,UACJ,SACA,SAC0B;AAC1B,SAAO,KAAK,QAAyB,iBAAiB;GACpD,QAAQ;GACR,MAAM,KAAK,UAAU,QAAQ;GAC7B,QAAQ,SAAS;GAClB,CAAC;;CAGJ,MAAM,UAAU,IAAY,SAA4C;AACtE,QAAM,KAAK,QAAc,iBAAiB,MAAM;GAC9C,QAAQ;GACR,QAAQ,SAAS;GAClB,CAAC;;CAGJ,MAAM,QACJ,SACA,SAC8B;AAC9B,SAAO,KAAK,QAA6B,oBAAoB;GAC3D,QAAQ;GACR,MAAM,KAAK,UAAU,QAAQ;GAC7B,QAAQ,SAAS;GAClB,CAAC;;CAGJ,MAAM,UACJ,MACA,SACe;AACf,QAAM,KAAK,QAAc,sBAAsB;GAC7C,QAAQ;GACR,MAAM,KAAK,UAAU,EAAE,MAAM,CAAC;GAC9B,QAAQ,SAAS;GAClB,CAAC;;CAGJ,MAAM,QACJ,MACA,SAC8B;AAC9B,SAAO,KAAK,QAA6B,oBAAoB,QAAQ,EACnE,QAAQ,SAAS,QAClB,CAAC"}