@yahoo/uds-create-config 5.42.3 → 5.43.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yahoo/uds-create-config",
-  "version": "5.42.3",
+  "version": "5.43.0",
   "private": false,
   "type": "module",
   "main": "./dist/index.js",
@@ -110,5 +110,5 @@
   "files": [
     "dist"
   ],
-  "udsSchemaVersion": 20261020173914
+  "udsSchemaVersion": 20261020183330
 }

package/dist/framework/registry-dir.js

@@ -1,69 +0,0 @@
-import { BUILD_DEFAULTS } from "../configs/build-options.js";
-//#region src/framework/registry-dir.ts
-/**
-* Where a project's build directories live, relative to the project root — the registry it pulls
-* into, the directory it writes to, and the one it is allowed to read from.
-*
-* One resolution rule each, shared by every consumer, because a default spelled at the call site is
-* a default that drifts: `.uds` was written out at eight of them before this.
-*
-* The registry half is shared by `uds pull` (writes the registry), `uds build` (regenerates linked
-* CSS from it), the bundler loaders (skip its files), and the push seal (excludes its files from a
-* consumer's own sealed sources): `build.registryDir` when the consumer sets one, else `registry/`
-* beside the system's components — `src/uds/registry` in the conventional layout.
-*/
-/** The prefix a system's sources are imported by (`@/uds`), for their types. */
-function resolveSourceAlias(buildOptions) {
-	return normalize(buildOptions?.sourceAlias ?? BUILD_DEFAULTS.sourceAlias);
-}
-/** The prefix a system's build output is imported by (`#uds`), mapped onto its `outDir`. */
-function resolveOutputAlias(buildOptions) {
-	return normalize(buildOptions?.outputAlias ?? BUILD_DEFAULTS.outputAlias);
-}
-/** Scanned rather than matched with `/\/+$/`: anchoring a repeated group at the end makes the engine
-*  backtrack across the whole run, which is quadratic on a path that is all slashes. */
-const normalize = (p) => {
-	const posix = p.replace(/\\/g, "/");
-	let end = posix.length;
-	while (end > 0 && posix[end - 1] === "/") end--;
-	return posix.slice(0, end);
-};
-/**
-* Project-root-relative POSIX path of the linked-system registry.
-*
-* Unset, it sits beside the system's own components: `registry/` under the root its `inputDir` names
-* (`components` itself dropped, so `src/uds/components` and `src/uds` both give `src/uds/registry`),
-* or under `src/uds` when none is declared. Linked sources are then imported the way the system's own
-* are, `@/uds/registry/<slug>/…` beside `@/uds/components/…`.
-*
-* Read from the AUTHORED settings only, never the derived `inputDir`: a loader that has nothing but a
-* built `config.json` has to land on the same directory the build did.
-*/
-function resolveRegistryDir(buildOptions) {
-	if (buildOptions?.registryDir) return normalize(buildOptions.registryDir);
-	const inputDir = buildOptions?.inputDir ? normalize(buildOptions.inputDir) : BUILD_DEFAULTS.inputRoot;
-	const root = inputDir === "components" ? "" : inputDir.replace(/\/components$/, "");
-	return root ? `${root}/registry` : "registry";
-}
-/**
-* Project-root-relative POSIX path of the build output directory.
-*
-* The schema's default unless the system says otherwise. A CLI `--output-dir` overrides both, which is
-* why this takes only the config: a scratch build is the caller's business, not the system's.
-*/
-function resolveOutDir(buildOptions) {
-	return normalize(buildOptions?.outDir ?? BUILD_DEFAULTS.outDir);
-}
-/**
-* Config-relative POSIX path of the directory every sealed file must live under, or `undefined` when
-* the system declares none.
-*
-* `undefined` is not a default in disguise — it is the answer that keeps the `uds/components/`
-* anchor convention in charge, so a config that never set this emits exactly what it emitted before.
-*/
-function resolveInputDir(buildOptions) {
-	if (!buildOptions?.inputDir) return void 0;
-	return normalize(buildOptions.inputDir);
-}
-//#endregion
-export { resolveInputDir, resolveOutDir, resolveOutputAlias, resolveRegistryDir, resolveSourceAlias };