@theholocron/tsdown-config 8.6.0 → 8.6.1

package/dist/presets/cli.js

@@ -1,4 +1,4 @@
-import { t as resolveEntry } from "../resolve-entry-DDrvshfq.js";
+import { n as resolveOutDir, t as resolveEntry } from "../resolve-entry-Bh8yS2Sn.js";
 import { defineConfig } from "tsdown";
 //#region presets/cli.ts
 /**
@@ -9,6 +9,7 @@ import { defineConfig } from "tsdown";
 function cli(options = {}) {
 	const merged = {
 		entry: ["src/cli.ts"],
+		outDir: "dist",
 		format: "esm",
 		dts: false,
 		clean: true,
@@ -18,7 +19,8 @@ function cli(options = {}) {
 	};
 	return defineConfig({
 		...merged,
-		entry: resolveEntry(merged.entry)
+		entry: resolveEntry(merged.entry),
+		outDir: resolveOutDir(merged.outDir ?? "dist")
 	});
 }
 var cli_default = cli();

package/dist/presets/library.js

@@ -1,4 +1,4 @@
-import { t as resolveEntry } from "../resolve-entry-DDrvshfq.js";
+import { n as resolveOutDir, t as resolveEntry } from "../resolve-entry-Bh8yS2Sn.js";
 import { defineConfig } from "tsdown";
 //#region presets/library.ts
 /**
@@ -18,6 +18,7 @@ import { defineConfig } from "tsdown";
 function library(options = {}) {
 	const merged = {
 		entry: ["src/index.ts"],
+		outDir: "dist",
 		format: "esm",
 		dts: true,
 		clean: true,
@@ -26,7 +27,8 @@ function library(options = {}) {
 	};
 	return defineConfig({
 		...merged,
-		entry: resolveEntry(merged.entry)
+		entry: resolveEntry(merged.entry),
+		outDir: resolveOutDir(merged.outDir ?? "dist")
 	});
 }
 /** Ready-to-use config for packages that need no customisation. */

package/dist/resolve-entry-Bh8yS2Sn.js

@@ -0,0 +1,39 @@
+import { resolve } from "node:path";
+//#region presets/resolve-entry.ts
+/**
+* tsdown resolves a config's relative paths — `entry` and, confirmed the
+* same way (clients#376's release: every package but `http-client`, the
+* one that still kept its own local `tsdown.config.ts`, published with an
+* empty `dist/` — the real build output landed in
+* `node_modules/@theholocron/tsdown-config/dist/presets/dist/` instead),
+* `outDir` too — 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
+* `entry`'s own version of this first surfaced, migrating a real repo off
+* its local file; `outDir` was never given the same treatment, and the
+* build silently "succeeded" — real file sizes, real log output — while
+* writing everything to a phantom location no `npm publish` would ever
+* pack). 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;
+}
+/** Same fix as {@link resolveEntry}, for the single-string `outDir` option. */
+function resolveOutDir(outDir) {
+	return resolve(process.cwd(), outDir);
+}
+//#endregion
+export { resolveOutDir as n, resolveEntry as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/tsdown-config",
-  "version": "8.6.0",
+  "version": "8.6.1",
   "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/tsconfig": "8.6.0",
-    "@theholocron/vitest-config": "8.6.0"
+    "@theholocron/vitest-config": "8.6.1",
+    "@theholocron/tsconfig": "8.6.1"
   },
   "exports": {
     ".": {

package/dist/resolve-entry-DDrvshfq.js

@@ -1,27 +0,0 @@
-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 };