@camstack/system 1.2.27 → 1.2.29

package/dist/builtins/sqlite-storage/sqlite-settings.addon.js

@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
 	[Symbol.toStringTag]: { value: "Module" }
 });
 const require_chunk = require("../../chunk-Cek0wNdY.js");
-const require_dist = require("../../dist-BxtIzexq.js");
+const require_dist = require("../../dist-CPmFYLqq.js");
 let node_crypto = require("node:crypto");
 let better_sqlite3 = require("better-sqlite3");
 better_sqlite3 = require_chunk.__toESM(better_sqlite3);
@@ -119,6 +119,18 @@ var SqliteSettingsBackend = class SqliteSettingsBackend {
 		this.db?.close();
 		this.db = null;
 	}
+	/**
+	* `data-store-provider` self-description — how the orchestrator names
+	* this engine in a log line, and (once collections declare an engine)
+	* how it picks between registrants.
+	*/
+	async getEngineInfo() {
+		return {
+			engineId: "sqlite",
+			kind: "relational",
+			displayName: "SQLite (WAL)"
+		};
+	}
 	async get({ namespace, collection, key }) {
 		const scoped = this.scopedName(namespace, collection);
 		const decl = this.requireDeclared(scoped);
@@ -605,8 +617,14 @@ var SqliteSettingsBackend = class SqliteSettingsBackend {
 //#endregion
 //#region src/builtins/sqlite-storage/sqlite-settings.addon.ts
 /**
-* SQLite Settings addon — provides persistent settings storage.
-* Capability: 'settings-store' (singleton)
+* SQLite Settings addon — the relational ENGINE behind the data door.
+*
+* Capability: `data-store-provider` (collection, internal). It does not
+* serve `settings-store`: that is the public door, owned by
+* storage-orchestrator, which dispatches here
+* ([D44](../../../../../docs/decisions/adr-0044.md)). Callers reach this
+* engine only through the door — which is the point, because it is what
+* makes the engine replaceable.
 */
 var SqliteSettingsAddon = class extends require_dist.BaseAddon {
 	backend = null;
@@ -635,7 +653,7 @@ var SqliteSettingsAddon = class extends require_dist.BaseAddon {
 		await this.backend.initialize();
 		this.ctx.logger.info("Initialized successfully");
 		return [{
-			capability: require_dist.settingsStoreCapability,
+			capability: require_dist.dataStoreProviderCapability,
 			provider: this.backend
 		}];
 	}

package/dist/builtins/sqlite-storage/sqlite-settings.addon.mjs

@@ -1,4 +1,4 @@
-import { Et as parseJsonUnknown, X as settingsStoreCapability, at as BaseAddon, c as RUNTIME_DEFAULTS, ht as asJsonObject, it as errMsg } from "../../dist-BXmFvn3h.mjs";
+import { Dt as parseJsonUnknown, at as errMsg, c as RUNTIME_DEFAULTS, gt as asJsonObject, ot as BaseAddon, x as dataStoreProviderCapability } from "../../dist-B7hOpr5i.mjs";
 import { randomUUID } from "node:crypto";
 import Database from "better-sqlite3";
 //#region src/builtins/sqlite-storage/sqlite-settings-backend.ts
@@ -113,6 +113,18 @@ var SqliteSettingsBackend = class SqliteSettingsBackend {
 		this.db?.close();
 		this.db = null;
 	}
+	/**
+	* `data-store-provider` self-description — how the orchestrator names
+	* this engine in a log line, and (once collections declare an engine)
+	* how it picks between registrants.
+	*/
+	async getEngineInfo() {
+		return {
+			engineId: "sqlite",
+			kind: "relational",
+			displayName: "SQLite (WAL)"
+		};
+	}
 	async get({ namespace, collection, key }) {
 		const scoped = this.scopedName(namespace, collection);
 		const decl = this.requireDeclared(scoped);
@@ -599,8 +611,14 @@ var SqliteSettingsBackend = class SqliteSettingsBackend {
 //#endregion
 //#region src/builtins/sqlite-storage/sqlite-settings.addon.ts
 /**
-* SQLite Settings addon — provides persistent settings storage.
-* Capability: 'settings-store' (singleton)
+* SQLite Settings addon — the relational ENGINE behind the data door.
+*
+* Capability: `data-store-provider` (collection, internal). It does not
+* serve `settings-store`: that is the public door, owned by
+* storage-orchestrator, which dispatches here
+* ([D44](../../../../../docs/decisions/adr-0044.md)). Callers reach this
+* engine only through the door — which is the point, because it is what
+* makes the engine replaceable.
 */
 var SqliteSettingsAddon = class extends BaseAddon {
 	backend = null;
@@ -629,7 +647,7 @@ var SqliteSettingsAddon = class extends BaseAddon {
 		await this.backend.initialize();
 		this.ctx.logger.info("Initialized successfully");
 		return [{
-			capability: settingsStoreCapability,
+			capability: dataStoreProviderCapability,
 			provider: this.backend
 		}];
 	}

package/dist/builtins/storage-orchestrator/data-store-dispatch.d.ts

@@ -0,0 +1,12 @@
+import { IDataStoreProvider, ISettingsStoreProvider } from '@camstack/types';
+/** How the dispatcher reaches the registered engines, read per call. */
+export type GetDataStoreEngines = () => readonly IDataStoreProvider[];
+/**
+ * Build the `settings-store` provider that fronts the registered engines.
+ *
+ * `getEngines` is read on every call, never captured: engines register
+ * during boot and a runner respawn replaces the instance, so a snapshot
+ * taken at construction time would go stale exactly when an addon crashed
+ * and came back.
+ */
+export declare function createDataStoreDispatch(getEngines: GetDataStoreEngines): ISettingsStoreProvider;

package/dist/builtins/storage-orchestrator/storage-orchestrator.addon.d.ts

@@ -25,16 +25,27 @@ export declare class StorageOrchestratorAddon extends BaseAddon<StorageOrchestra
     protected onInitialize(): Promise<ProviderRegistration[]>;
     protected onShutdown(): Promise<void>;
     /**
-     * Resolve the live `ISettingsBackend` from the capability registry
-     * and wrap it in a `SqliteLocationStore`. Returns `null` when the
-     * settings-store cap isn't registered yet — the service falls back
-     * to in-memory only. Production boot order (sqlite-settings runs
-     * before the orchestrator) makes this the rare path.
+     * Resolve the live engine from the capability registry and wrap it in a
+     * `SqliteLocationStore`. Returns `null` when no engine has registered
+     * yet — the service falls back to in-memory only. Production boot order
+     * (`data-store-provider` precedes `storage` in `INFRA_CAPABILITIES`)
+     * makes this the rare path.
+     *
+     * Reads the ENGINE, not the `settings-store` singleton: since D44 this
+     * addon *is* that singleton, so asking the registry for it would hand
+     * the orchestrator its own dispatcher and route its location table back
+     * through itself.
+     *
+     * The `ensureTable` / `tableInsert` reach-around below is the B2 bypass,
+     * still open: those six methods live on the concrete backend and on no
+     * cap. Promoting them to the door is a separate task; until then this
+     * holds the engine object directly, which only works because the engine
+     * is in-process on this node.
      */
     private resolveLocationStore;
     /**
-     * Late-wire the persistence store once the `settings-store` cap registers.
-     * Production boot order means the store is usually absent at
+     * Late-wire the persistence store once a `data-store-provider` engine
+     * registers. Production boot order means the store is usually absent at
      * `onInitialize`; this runs on every `capability:provider-registered`
      * event until it succeeds. Single-flighted + idempotent (the service
      * ignores a second attach). Without this, operator edits (e.g. a

package/dist/builtins/storage-orchestrator/storage-orchestrator.addon.js

@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
 	[Symbol.toStringTag]: { value: "Module" }
 });
 const require_chunk = require("../../chunk-Cek0wNdY.js");
-const require_dist = require("../../dist-BxtIzexq.js");
+const require_dist = require("../../dist-CPmFYLqq.js");
 let node_path = require("node:path");
 node_path = require_chunk.__toESM(node_path);
 let node_fs_promises = require("node:fs/promises");
@@ -730,6 +730,53 @@ async function collectProviderInfos(providers, onError) {
 	return out;
 }
 //#endregion
+//#region src/builtins/storage-orchestrator/data-store-dispatch.ts
+/**
+* Pick the engine to serve a call.
+*
+* Today the rule is "the only one there is". Two cases are refused rather
+* than guessed:
+*
+*  - **none registered** — resolving to a no-op would make every read
+*    answer `undefined` and every write disappear, which reads exactly
+*    like an empty database;
+*  - **more than one** — there is no routing rule yet. The `engine` hint
+*    on `declareCollection` is what will choose, and until it exists a
+*    silent pick would send a collection to whichever engine happened to
+*    register first.
+*/
+function resolveEngine(getEngines) {
+	const engines = getEngines();
+	if (engines.length === 0) throw new Error("settings-store: no data-store-provider engine is registered — the data door has nothing behind it");
+	if (engines.length > 1) throw new Error(`settings-store: ${engines.length} data-store-provider engines are registered and there is no routing rule yet — declare the engine on the collection first`);
+	const engine = engines[0];
+	if (!engine) throw new Error("settings-store: data-store-provider collection yielded an empty entry");
+	return engine;
+}
+/**
+* Build the `settings-store` provider that fronts the registered engines.
+*
+* `getEngines` is read on every call, never captured: engines register
+* during boot and a runner respawn replaces the instance, so a snapshot
+* taken at construction time would go stale exactly when an addon crashed
+* and came back.
+*/
+function createDataStoreDispatch(getEngines) {
+	const engine = async () => resolveEngine(getEngines);
+	return {
+		get: async (input) => (await engine()).get(input),
+		set: async (input) => (await engine()).set(input),
+		query: async (input) => (await engine()).query(input),
+		insert: async (input) => (await engine()).insert(input),
+		update: async (input) => (await engine()).update(input),
+		delete: async (input) => (await engine()).delete(input),
+		count: async (input) => (await engine()).count(input),
+		histogram: async (input) => (await engine()).histogram(input),
+		isEmpty: async (input) => (await engine()).isEmpty(input),
+		declareCollection: async (input) => (await engine()).declareCollection(input)
+	};
+}
+//#endregion
 //#region src/builtins/storage-orchestrator/storage-pressure-manager.ts
 var DEFAULT_MAX_ROUNDS = 8;
 var DEFAULT_HYSTERESIS_PERCENT = 1;
@@ -891,6 +938,7 @@ var StoragePressureManager = class {
 * Task 7 will migrate consumers off the legacy storage shim.
 */
 var STORAGE_PROVIDER_CAP_NAME = "storage-provider";
+var DATA_STORE_PROVIDER_CAP_NAME = "data-store-provider";
 var STORAGE_EVICTABLE_CAP_NAME = "storage-evictable";
 /**
 * Single-node default: existing node-local locations live on the hub.
@@ -935,6 +983,11 @@ var StorageOrchestratorAddon = class extends require_dist.BaseAddon {
 			if (!reg) return [];
 			return reg.getCollection(STORAGE_PROVIDER_CAP_NAME);
 		};
+		const getEngines = () => {
+			const reg = this.ctx.kernel.capabilityRegistry;
+			if (!reg) return [];
+			return reg.getCollection(DATA_STORE_PROVIDER_CAP_NAME);
+		};
 		const locationStore = this.resolveLocationStore();
 		const service = new StorageOrchestratorService(this.ctx.logger, getProviders, locationStore, this.ctx.kernel.localNodeId ?? "hub", (nodeId) => {
 			const proxy = this.ctx.kernel.resolveNodeCapability?.("storage-provider", nodeId);
@@ -1126,6 +1179,9 @@ var StorageOrchestratorAddon = class extends require_dist.BaseAddon {
 		return [{
 			capability: require_dist.storageCapability,
 			provider
+		}, {
+			capability: require_dist.settingsStoreCapability,
+			provider: createDataStoreDispatch(getEngines)
 		}];
 	}
 	async onShutdown() {
@@ -1142,18 +1198,29 @@ var StorageOrchestratorAddon = class extends require_dist.BaseAddon {
 		this.service = null;
 	}
 	/**
-	* Resolve the live `ISettingsBackend` from the capability registry
-	* and wrap it in a `SqliteLocationStore`. Returns `null` when the
-	* settings-store cap isn't registered yet — the service falls back
-	* to in-memory only. Production boot order (sqlite-settings runs
-	* before the orchestrator) makes this the rare path.
+	* Resolve the live engine from the capability registry and wrap it in a
+	* `SqliteLocationStore`. Returns `null` when no engine has registered
+	* yet — the service falls back to in-memory only. Production boot order
+	* (`data-store-provider` precedes `storage` in `INFRA_CAPABILITIES`)
+	* makes this the rare path.
+	*
+	* Reads the ENGINE, not the `settings-store` singleton: since D44 this
+	* addon *is* that singleton, so asking the registry for it would hand
+	* the orchestrator its own dispatcher and route its location table back
+	* through itself.
+	*
+	* The `ensureTable` / `tableInsert` reach-around below is the B2 bypass,
+	* still open: those six methods live on the concrete backend and on no
+	* cap. Promoting them to the door is a separate task; until then this
+	* holds the engine object directly, which only works because the engine
+	* is in-process on this node.
 	*/
 	resolveLocationStore(quiet = false) {
 		const reg = this.ctx.kernel.capabilityRegistry;
 		if (!reg) return null;
-		const backend = reg.getSingleton("settings-store");
+		const backend = reg.getCollection(DATA_STORE_PROVIDER_CAP_NAME)[0];
 		if (!backend) {
-			if (!quiet) this.ctx.logger.warn("storage-orchestrator: no settings-store provider yet — running in-memory until it registers");
+			if (!quiet) this.ctx.logger.warn("storage-orchestrator: no data-store-provider engine yet — running in-memory until one registers");
 			return null;
 		}
 		if (!backend.ensureTable || !backend.tableInsert) {
@@ -1163,8 +1230,8 @@ var StorageOrchestratorAddon = class extends require_dist.BaseAddon {
 		return new SqliteLocationStore(backend);
 	}
 	/**
-	* Late-wire the persistence store once the `settings-store` cap registers.
-	* Production boot order means the store is usually absent at
+	* Late-wire the persistence store once a `data-store-provider` engine
+	* registers. Production boot order means the store is usually absent at
 	* `onInitialize`; this runs on every `capability:provider-registered`
 	* event until it succeeds. Single-flighted + idempotent (the service
 	* ignores a second attach). Without this, operator edits (e.g. a
@@ -1178,7 +1245,7 @@ var StorageOrchestratorAddon = class extends require_dist.BaseAddon {
 		if (this.storeWireInFlight) return this.storeWireInFlight;
 		const store = this.resolveLocationStore(true);
 		if (!store) return;
-		this.ctx.logger.info("storage-orchestrator: settings-store now available — wiring persistence");
+		this.ctx.logger.info("storage-orchestrator: data-store engine now available — wiring persistence");
 		this.storeWireInFlight = service.attachStore(store).then(() => this.seedFromDeclarations()).catch((err) => {
 			this.ctx.logger.error("storage-orchestrator: attachStore failed", { meta: { error: err instanceof Error ? err.message : String(err) } });
 		}).finally(() => {

package/dist/builtins/storage-orchestrator/storage-orchestrator.addon.mjs

@@ -1,4 +1,4 @@
-import { Q as storageCapability, Tt as parseJsonObject, at as BaseAddon, d as StorageLocationTypeSchema } from "../../dist-BXmFvn3h.mjs";
+import { $ as storageCapability, Et as parseJsonObject, Z as settingsStoreCapability, d as StorageLocationTypeSchema, ot as BaseAddon } from "../../dist-B7hOpr5i.mjs";
 import * as path$1 from "node:path";
 import * as fs from "node:fs/promises";
 import { buildStorageLocationRegistry } from "@camstack/system";
@@ -723,6 +723,53 @@ async function collectProviderInfos(providers, onError) {
 	return out;
 }
 //#endregion
+//#region src/builtins/storage-orchestrator/data-store-dispatch.ts
+/**
+* Pick the engine to serve a call.
+*
+* Today the rule is "the only one there is". Two cases are refused rather
+* than guessed:
+*
+*  - **none registered** — resolving to a no-op would make every read
+*    answer `undefined` and every write disappear, which reads exactly
+*    like an empty database;
+*  - **more than one** — there is no routing rule yet. The `engine` hint
+*    on `declareCollection` is what will choose, and until it exists a
+*    silent pick would send a collection to whichever engine happened to
+*    register first.
+*/
+function resolveEngine(getEngines) {
+	const engines = getEngines();
+	if (engines.length === 0) throw new Error("settings-store: no data-store-provider engine is registered — the data door has nothing behind it");
+	if (engines.length > 1) throw new Error(`settings-store: ${engines.length} data-store-provider engines are registered and there is no routing rule yet — declare the engine on the collection first`);
+	const engine = engines[0];
+	if (!engine) throw new Error("settings-store: data-store-provider collection yielded an empty entry");
+	return engine;
+}
+/**
+* Build the `settings-store` provider that fronts the registered engines.
+*
+* `getEngines` is read on every call, never captured: engines register
+* during boot and a runner respawn replaces the instance, so a snapshot
+* taken at construction time would go stale exactly when an addon crashed
+* and came back.
+*/
+function createDataStoreDispatch(getEngines) {
+	const engine = async () => resolveEngine(getEngines);
+	return {
+		get: async (input) => (await engine()).get(input),
+		set: async (input) => (await engine()).set(input),
+		query: async (input) => (await engine()).query(input),
+		insert: async (input) => (await engine()).insert(input),
+		update: async (input) => (await engine()).update(input),
+		delete: async (input) => (await engine()).delete(input),
+		count: async (input) => (await engine()).count(input),
+		histogram: async (input) => (await engine()).histogram(input),
+		isEmpty: async (input) => (await engine()).isEmpty(input),
+		declareCollection: async (input) => (await engine()).declareCollection(input)
+	};
+}
+//#endregion
 //#region src/builtins/storage-orchestrator/storage-pressure-manager.ts
 var DEFAULT_MAX_ROUNDS = 8;
 var DEFAULT_HYSTERESIS_PERCENT = 1;
@@ -884,6 +931,7 @@ var StoragePressureManager = class {
 * Task 7 will migrate consumers off the legacy storage shim.
 */
 var STORAGE_PROVIDER_CAP_NAME = "storage-provider";
+var DATA_STORE_PROVIDER_CAP_NAME = "data-store-provider";
 var STORAGE_EVICTABLE_CAP_NAME = "storage-evictable";
 /**
 * Single-node default: existing node-local locations live on the hub.
@@ -928,6 +976,11 @@ var StorageOrchestratorAddon = class extends BaseAddon {
 			if (!reg) return [];
 			return reg.getCollection(STORAGE_PROVIDER_CAP_NAME);
 		};
+		const getEngines = () => {
+			const reg = this.ctx.kernel.capabilityRegistry;
+			if (!reg) return [];
+			return reg.getCollection(DATA_STORE_PROVIDER_CAP_NAME);
+		};
 		const locationStore = this.resolveLocationStore();
 		const service = new StorageOrchestratorService(this.ctx.logger, getProviders, locationStore, this.ctx.kernel.localNodeId ?? "hub", (nodeId) => {
 			const proxy = this.ctx.kernel.resolveNodeCapability?.("storage-provider", nodeId);
@@ -1119,6 +1172,9 @@ var StorageOrchestratorAddon = class extends BaseAddon {
 		return [{
 			capability: storageCapability,
 			provider
+		}, {
+			capability: settingsStoreCapability,
+			provider: createDataStoreDispatch(getEngines)
 		}];
 	}
 	async onShutdown() {
@@ -1135,18 +1191,29 @@ var StorageOrchestratorAddon = class extends BaseAddon {
 		this.service = null;
 	}
 	/**
-	* Resolve the live `ISettingsBackend` from the capability registry
-	* and wrap it in a `SqliteLocationStore`. Returns `null` when the
-	* settings-store cap isn't registered yet — the service falls back
-	* to in-memory only. Production boot order (sqlite-settings runs
-	* before the orchestrator) makes this the rare path.
+	* Resolve the live engine from the capability registry and wrap it in a
+	* `SqliteLocationStore`. Returns `null` when no engine has registered
+	* yet — the service falls back to in-memory only. Production boot order
+	* (`data-store-provider` precedes `storage` in `INFRA_CAPABILITIES`)
+	* makes this the rare path.
+	*
+	* Reads the ENGINE, not the `settings-store` singleton: since D44 this
+	* addon *is* that singleton, so asking the registry for it would hand
+	* the orchestrator its own dispatcher and route its location table back
+	* through itself.
+	*
+	* The `ensureTable` / `tableInsert` reach-around below is the B2 bypass,
+	* still open: those six methods live on the concrete backend and on no
+	* cap. Promoting them to the door is a separate task; until then this
+	* holds the engine object directly, which only works because the engine
+	* is in-process on this node.
 	*/
 	resolveLocationStore(quiet = false) {
 		const reg = this.ctx.kernel.capabilityRegistry;
 		if (!reg) return null;
-		const backend = reg.getSingleton("settings-store");
+		const backend = reg.getCollection(DATA_STORE_PROVIDER_CAP_NAME)[0];
 		if (!backend) {
-			if (!quiet) this.ctx.logger.warn("storage-orchestrator: no settings-store provider yet — running in-memory until it registers");
+			if (!quiet) this.ctx.logger.warn("storage-orchestrator: no data-store-provider engine yet — running in-memory until one registers");
 			return null;
 		}
 		if (!backend.ensureTable || !backend.tableInsert) {
@@ -1156,8 +1223,8 @@ var StorageOrchestratorAddon = class extends BaseAddon {
 		return new SqliteLocationStore(backend);
 	}
 	/**
-	* Late-wire the persistence store once the `settings-store` cap registers.
-	* Production boot order means the store is usually absent at
+	* Late-wire the persistence store once a `data-store-provider` engine
+	* registers. Production boot order means the store is usually absent at
 	* `onInitialize`; this runs on every `capability:provider-registered`
 	* event until it succeeds. Single-flighted + idempotent (the service
 	* ignores a second attach). Without this, operator edits (e.g. a
@@ -1171,7 +1238,7 @@ var StorageOrchestratorAddon = class extends BaseAddon {
 		if (this.storeWireInFlight) return this.storeWireInFlight;
 		const store = this.resolveLocationStore(true);
 		if (!store) return;
-		this.ctx.logger.info("storage-orchestrator: settings-store now available — wiring persistence");
+		this.ctx.logger.info("storage-orchestrator: data-store engine now available — wiring persistence");
 		this.storeWireInFlight = service.attachStore(store).then(() => this.seedFromDeclarations()).catch((err) => {
 			this.ctx.logger.error("storage-orchestrator: attachStore failed", { meta: { error: err instanceof Error ? err.message : String(err) } });
 		}).finally(() => {

package/dist/builtins/system-config/system-config.addon.js

@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
 	[Symbol.toStringTag]: { value: "Module" }
 });
 require("../../chunk-Cek0wNdY.js");
-const require_dist = require("../../dist-BxtIzexq.js");
+const require_dist = require("../../dist-CPmFYLqq.js");
 //#region src/builtins/system-config/system-config.addon.ts
 /**
 * Built-in `system-config` addon — Phase 4 of the settings redesign.

package/dist/builtins/system-config/system-config.addon.mjs

@@ -1,4 +1,4 @@
-import { St as hydrateSchema, at as BaseAddon, it as errMsg } from "../../dist-BXmFvn3h.mjs";
+import { Ct as hydrateSchema, at as errMsg, ot as BaseAddon } from "../../dist-B7hOpr5i.mjs";
 //#region src/builtins/system-config/system-config.addon.ts
 /**
 * Built-in `system-config` addon — Phase 4 of the settings redesign.

package/dist/builtins/winston-logging/index.js

@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
 	[Symbol.toStringTag]: { value: "Module" }
 });
 const require_chunk = require("../../chunk-Cek0wNdY.js");
-const require_dist = require("../../dist-BxtIzexq.js");
+const require_dist = require("../../dist-CPmFYLqq.js");
 const require_formatter = require("../../formatter-DqAKDlvN.js");
 let node_path = require("node:path");
 node_path = require_chunk.__toESM(node_path);

package/dist/builtins/winston-logging/index.mjs

@@ -1,4 +1,4 @@
-import { at as BaseAddon, z as logDestinationCapability } from "../../dist-BXmFvn3h.mjs";
+import { B as logDestinationCapability, ot as BaseAddon } from "../../dist-B7hOpr5i.mjs";
 import { t as formatLogLine } from "../../formatter-B7qW8bPJ.mjs";
 import * as path$1 from "node:path";
 import path from "node:path";