@theholocron/tsdown-config 8.4.3 → 8.4.5

package/dist/presets/cli.js

@@ -1,3 +1,4 @@
+import { t as resolveEntry } from "../resolve-entry-DDrvshfq.js";
 import { defineConfig } from "tsdown";
 //#region presets/cli.ts
 /**
@@ -6,7 +7,7 @@ import { defineConfig } from "tsdown";
 * No type declarations — binaries don't need them.
 */
 function cli(options = {}) {
-	return defineConfig({
+	const merged = {
 		entry: ["src/cli.ts"],
 		format: "esm",
 		dts: false,
@@ -14,6 +15,10 @@ function cli(options = {}) {
 		sourcemap: true,
 		banner: { js: "#!/usr/bin/env node" },
 		...options
+	};
+	return defineConfig({
+		...merged,
+		entry: resolveEntry(merged.entry)
 	});
 }
 var cli_default = cli();

package/dist/presets/library.js

@@ -1,3 +1,4 @@
+import { t as resolveEntry } from "../resolve-entry-DDrvshfq.js";
 import { defineConfig } from "tsdown";
 //#region presets/library.ts
 /**
@@ -5,13 +6,17 @@ import { defineConfig } from "tsdown";
 * Single entry point, generates types, does not bundle @theholocron/* peers.
 */
 function library(options = {}) {
-	return defineConfig({
+	const merged = {
 		entry: ["src/index.ts"],
 		format: "esm",
 		dts: true,
 		clean: true,
 		deps: { neverBundle: [/^@theholocron\//] },
 		...options
+	};
+	return defineConfig({
+		...merged,
+		entry: resolveEntry(merged.entry)
 	});
 }
 /** Ready-to-use config for packages that need no customisation. */

package/dist/resolve-entry-DDrvshfq.js

@@ -0,0 +1,27 @@
+import { resolve } from "node:path";
+//#region presets/resolve-entry.ts
+/**
+* tsdown resolves a config's relative `entry` paths against the config
+* file's own directory, not the invoking `cwd` — fine for a package's own
+* local `tsdown.config.ts` (same directory as `src/`), but wrong the moment
+* `--config` points at this shared preset's own location deep in
+* `node_modules` (astromech's config-resolution mechanism, holocron#749/
+* #750/#680 — that's exactly how this surfaced, migrating a real repo off
+* its local file). An absolute path sidesteps the ambiguity entirely, in
+* both cases: `process.cwd()` is always the actual package directory tsdown
+* was invoked from, regardless of where the config *module* lives on disk.
+*
+* Only `string` and `string[]` are resolved — the only shapes any preset
+* here (or any known consumer's override) actually passes. tsdown's own
+* `entry` type also allows a `Record<string, string | string[]>` (named
+* multi-entry builds) and glob negation patterns (`!foo`); neither is used
+* anywhere in this org today, so both pass through unresolved rather than
+* guessing at a generalization nothing yet exercises.
+*/
+function resolveEntry(entry) {
+	if (typeof entry === "string") return resolve(process.cwd(), entry);
+	if (Array.isArray(entry) && entry.every((e) => typeof e === "string")) return entry.map((e) => resolve(process.cwd(), e));
+	return entry;
+}
+//#endregion
+export { resolveEntry as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/tsdown-config",
-  "version": "8.4.3",
+  "version": "8.4.5",
   "description": "Shared tsdown configurations for @theholocron packages.",
   "homepage": "https://github.com/theholocron/configs/tree/main/packages/tsdown-config#readme",
   "bugs": "https://github.com/theholocron/configs/issues",
@@ -25,8 +25,8 @@
     "tsdown": "^0.22.14",
     "typescript": "^5.9.3",
     "vitest": "^4.1.10",
-    "@theholocron/vitest-config": "8.4.3",
-    "@theholocron/tsconfig": "8.4.3"
+    "@theholocron/tsconfig": "8.4.5",
+    "@theholocron/vitest-config": "8.4.5"
   },
   "exports": {
     ".": {