@theholocron/datapad 5.0.0-alpha.9 → 5.0.0-alpha.90

package/README.md

@@ -51,6 +51,22 @@ Loads the first `<name>.config.<ext>` found in `cwd`. Probe order is
 file"; a file that exists but cannot be parsed / loaded / has no default
 export throws `ConfigFileError`.
 
+### `loadConfigFromContent<T>({ dir, content, name, extension })`
+
+Loads config from content that didn't come from a file already on disk —
+writes it to `<dir>/<name>.config.<extension>` first, then loads it through
+the exact same internals `loadConfigFile` uses for a file it discovered
+itself. `dir` matters: it's what upward `node_modules` resolution sees, so
+content that does `import { defineConfig } from "@theholocron/cli"` only
+resolves if `dir` sits under a tree where that package is a real
+dependency. Callers own creating and cleaning up `dir`. Returns
+`{ config, filepath }`; throws `ConfigFileError` the same way
+`loadConfigFile` does on a parse/load failure.
+
+Built for `@theholocron/sentinel`'s `validateConfig()` — it fetches a
+repo's `holocron.config.*` from GitHub's API, not a local checkout, but
+still needs the fetched content to execute as a real module.
+
 ### `loadLayered<T>({ cwd, name, fallback?, extensions? })`
 
 `<name>.config.*` layered over the `[fallback.key]` of

package/dist/index.d.mts

@@ -31,8 +31,10 @@ declare class ConfigFileError extends Error {
 //#endregion
 //#region src/load.d.ts
 /**
- * Discover and load `<name>.config.*` files. Holocron-agnostic — no
- * schema, no validation, no defaults. Consumers layer those on top.
+ * Discover and load `<name>.config.*` files, or load one from content that
+ * didn't come from a file at all ({@link loadConfigFromContent}).
+ * Holocron-agnostic — no schema, no validation, no defaults. Consumers
+ * layer those on top.
  *
  * Probe order is **TS-first**: `.ts` → `.js` → `.mjs` → `.cjs` → `.json`.
  * TS is loaded through `tsx`'s `tsImport` (a runtime dependency) so a
@@ -84,6 +86,34 @@ interface LayeredResult<T> {
  * when neither source resolves.
  */
 declare function loadLayered<T>(opts: LoadLayeredOptions): Promise<LayeredResult<T> | null>;
+interface LoadConfigFromContentOptions {
+  /**
+   * Directory to write `<name>.config.<extension>` into before loading —
+   * this is what upward `node_modules` resolution sees, so a config that
+   * does `import { defineConfig } from "@theholocron/cli"` only resolves
+   * if `dir` sits under a tree where that package is a real dependency.
+   * Callers own creating and cleaning up `dir` — this function only
+   * writes the one file into it.
+   */
+  dir: string;
+  /** Raw file content — not necessarily sourced from a local file at all (a network fetch, a git blob, …). */
+  content: string;
+  /** Base name — `"holocron"` writes `holocron.config.<extension>`. */
+  name: string;
+  /** Which of `DEFAULT_EXTENSIONS` `content` is — determines how it's interpreted (ts/js/mjs/cjs parsed as a module, json as `JSON.parse`). */
+  extension: string;
+}
+/**
+ * Load config from content that didn't come from a file already on disk —
+ * writes it to `<dir>/<name>.config.<extension>` first, then loads it
+ * through the exact same path {@link loadConfigFile} uses for a file it
+ * discovered itself. Exists because sourcing config content from somewhere
+ * other than the local filesystem (a GitHub API fetch, for one — see
+ * `@theholocron/sentinel`) doesn't change what loading it correctly means:
+ * a `.ts` config still needs real module resolution, `defineConfig` import
+ * included, not a re-implemented parser.
+ */
+declare function loadConfigFromContent<T>(opts: LoadConfigFromContentOptions): Promise<Loaded<T>>;
 //#endregion
 //#region src/merge.d.ts
 /**
@@ -98,4 +128,4 @@ declare function loadLayered<T>(opts: LoadLayeredOptions): Promise<LayeredResult
  */
 declare function mergeConfig<T>(base: T, override: unknown): T;
 //#endregion
-export { ConfigFileError, DEFAULT_EXTENSIONS, type LayeredResult, type LoadConfigFileOptions, type LoadLayeredOptions, type Loaded, createDefineConfig, loadConfigFile, loadLayered, mergeConfig };
+export { ConfigFileError, DEFAULT_EXTENSIONS, type LayeredResult, type LoadConfigFileOptions, type LoadConfigFromContentOptions, type LoadLayeredOptions, type Loaded, createDefineConfig, loadConfigFile, loadConfigFromContent, loadLayered, mergeConfig };

package/dist/index.mjs

@@ -1,4 +1,4 @@
-import { readFile, stat } from "node:fs/promises";
+import { readFile, stat, writeFile } from "node:fs/promises";
 import { join } from "node:path";
 import { pathToFileURL } from "node:url";
 //#region src/define.ts
@@ -65,8 +65,10 @@ function isPlainObject(value) {
 //#endregion
 //#region src/load.ts
 /**
-* Discover and load `<name>.config.*` files. Holocron-agnostic — no
-* schema, no validation, no defaults. Consumers layer those on top.
+* Discover and load `<name>.config.*` files, or load one from content that
+* didn't come from a file at all ({@link loadConfigFromContent}).
+* Holocron-agnostic — no schema, no validation, no defaults. Consumers
+* layer those on top.
 *
 * Probe order is **TS-first**: `.ts` → `.js` → `.mjs` → `.cjs` → `.json`.
 * TS is loaded through `tsx`'s `tsImport` (a runtime dependency) so a
@@ -127,6 +129,24 @@ async function loadLayered(opts) {
 		sources
 	};
 }
+/**
+* Load config from content that didn't come from a file already on disk —
+* writes it to `<dir>/<name>.config.<extension>` first, then loads it
+* through the exact same path {@link loadConfigFile} uses for a file it
+* discovered itself. Exists because sourcing config content from somewhere
+* other than the local filesystem (a GitHub API fetch, for one — see
+* `@theholocron/sentinel`) doesn't change what loading it correctly means:
+* a `.ts` config still needs real module resolution, `defineConfig` import
+* included, not a re-implemented parser.
+*/
+async function loadConfigFromContent(opts) {
+	const filepath = join(opts.dir, `${opts.name}.config.${opts.extension}`);
+	await writeFile(filepath, opts.content, "utf8");
+	return {
+		config: await loadFile(filepath, opts.extension),
+		filepath
+	};
+}
 async function loadFile(filepath, ext) {
 	if (ext === "json") return loadJson(filepath);
 	return extractDefault(filepath, ext === "ts" ? await importTs(filepath) : await importModule(filepath));
@@ -188,4 +208,4 @@ async function isFile(path) {
 }
 const message = (err) => err instanceof Error ? err.message : String(err);
 //#endregion
-export { ConfigFileError, DEFAULT_EXTENSIONS, createDefineConfig, loadConfigFile, loadLayered, mergeConfig };
+export { ConfigFileError, DEFAULT_EXTENSIONS, createDefineConfig, loadConfigFile, loadConfigFromContent, loadLayered, mergeConfig };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/datapad",
-  "version": "5.0.0-alpha.9",
+  "version": "5.0.0-alpha.90",
   "description": "Generic config-file loading for Holocron — discover, load (JSON/JS/TS/ESM/CJS), and merge <name>.config.* files with a typed defineConfig.",
   "keywords": [
     "config",
@@ -35,10 +35,10 @@
     "tsx": "4.23.12"
   },
   "devDependencies": {
-    "@theholocron/eslint-config": "^8.0.0",
-    "@theholocron/tsconfig": "^8.0.0",
-    "@theholocron/tsdown-config": "^8.0.0",
-    "@theholocron/vitest-config": "^8.0.0",
+    "@theholocron/eslint-config": "^8.6.0",
+    "@theholocron/tsconfig": "^8.4.5",
+    "@theholocron/tsdown-config": "^8.4.5",
+    "@theholocron/vitest-config": "^8.4.5",
     "@types/node": "^26",
     "@vitest/coverage-v8": "^4.1.11",
     "@vitest/eslint-plugin": "^1.6.27",