@burojs/ui-shadcn 0.3.0 → 0.4.0

package/dist/layout/theme-storage-key.cjs

@@ -1,12 +1,7 @@
-'use strict';
+Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
+//#region src/layout/theme-storage-key.ts
+const THEME_STORAGE_KEY = "buro-theme";
+//#endregion
+exports.THEME_STORAGE_KEY = THEME_STORAGE_KEY;
 
-var chunkVXJAXJ3U_cjs = require('../chunk-VXJAXJ3U.cjs');
-
-
-
-Object.defineProperty(exports, "THEME_STORAGE_KEY", {
-  enumerable: true,
-  get: function () { return chunkVXJAXJ3U_cjs.THEME_STORAGE_KEY; }
-});
-//# sourceMappingURL=theme-storage-key.cjs.map
 //# sourceMappingURL=theme-storage-key.cjs.map

package/dist/layout/theme-storage-key.cjs.map

@@ -1 +1 @@
-{"version":3,"sources":[],"names":[],"mappings":"","file":"theme-storage-key.cjs"}
+{"version":3,"file":"theme-storage-key.cjs","names":[],"sources":["../../src/layout/theme-storage-key.ts"],"sourcesContent":["/**\n * The ONE localStorage key every theme-aware place in the app must agree on.\n * Exported so nothing re-types the string — two files agreeing on a literal\n * is how they drift.\n *\n * Deliberately its own module: no `'use client'`, no React import, nothing\n * that would pull in `use-theme.ts`'s hook (or the rest of the kit's client\n * component tree). That matters because the consumer that needs this\n * constant outside a hook is a pre-paint bootstrap `<script>` in a Next root\n * `app/layout.tsx` — a Server Component, which cannot itself carry\n * `'use client'`. `examples/next/app/layout.tsx` is that consumer, and after\n * SP9 deleted `apps/playground` it is the only one; a plain-HTML host has the\n * same need but no module graph to satisfy it from, which is why\n * `examples/marketplace-ops/index.html` spells the key as a literal and pins\n * it against this constant in a test instead.\n * Importing from the package's main entry (`@burojs/ui-shadcn`)\n * there fails Next's server/client boundary check, because that entry\n * bundles the whole kit — including many components that call hooks —\n * into one file without a top-level `'use client'` directive (the bundler\n * drops it when merging multiple client modules together — true of tsdown,\n * as it was of tsup). Importing this file\n * directly via the `@burojs/ui-shadcn/theme-storage-key` subpath sidesteps\n * that: it has no hooks, so a Server Component can import the real string\n * value at build/SSR time. `use-theme.ts` re-exports the same constant for\n * everyone else, so there is exactly one literal in the whole codebase.\n */\nexport const THEME_STORAGE_KEY = 'buro-theme';\n"],"mappings":";;AA0BA,MAAa,oBAAoB"}

package/dist/layout/theme-storage-key.d.cts

@@ -1,23 +1,2 @@
-/**
- * The ONE localStorage key every theme-aware place in the app must agree on.
- * Exported so nothing re-types the string — two files agreeing on a literal
- * is how they drift.
- *
- * Deliberately its own module: no `'use client'`, no React import, nothing
- * that would pull in `use-theme.ts`'s hook (or the rest of the kit's client
- * component tree). That matters because the ONE consumer that needs this
- * constant outside a hook is the bootstrap `<script>` in the playground's
- * root `app/layout.tsx` — a Server Component, which cannot itself carry
- * `'use client'`. Importing from the package's main entry (`@burojs/ui-shadcn`)
- * there fails Next's server/client boundary check, because that entry
- * bundles the whole kit — including many components that call hooks —
- * into one file without a top-level `'use client'` directive (tsup drops it
- * when bundling multiple client modules together). Importing this file
- * directly via the `@burojs/ui-shadcn/theme-storage-key` subpath sidesteps
- * that: it has no hooks, so a Server Component can import the real string
- * value at build/SSR time. `use-theme.ts` re-exports the same constant for
- * everyone else, so there is exactly one literal in the whole codebase.
- */
-declare const THEME_STORAGE_KEY = "buro-theme";
-
-export { THEME_STORAGE_KEY };
+import { t as THEME_STORAGE_KEY } from "../theme-storage-key-pYlp4aDS.cjs";
+export { THEME_STORAGE_KEY };

package/dist/layout/theme-storage-key.d.ts

@@ -1,23 +1,2 @@
-/**
- * The ONE localStorage key every theme-aware place in the app must agree on.
- * Exported so nothing re-types the string — two files agreeing on a literal
- * is how they drift.
- *
- * Deliberately its own module: no `'use client'`, no React import, nothing
- * that would pull in `use-theme.ts`'s hook (or the rest of the kit's client
- * component tree). That matters because the ONE consumer that needs this
- * constant outside a hook is the bootstrap `<script>` in the playground's
- * root `app/layout.tsx` — a Server Component, which cannot itself carry
- * `'use client'`. Importing from the package's main entry (`@burojs/ui-shadcn`)
- * there fails Next's server/client boundary check, because that entry
- * bundles the whole kit — including many components that call hooks —
- * into one file without a top-level `'use client'` directive (tsup drops it
- * when bundling multiple client modules together). Importing this file
- * directly via the `@burojs/ui-shadcn/theme-storage-key` subpath sidesteps
- * that: it has no hooks, so a Server Component can import the real string
- * value at build/SSR time. `use-theme.ts` re-exports the same constant for
- * everyone else, so there is exactly one literal in the whole codebase.
- */
-declare const THEME_STORAGE_KEY = "buro-theme";
-
-export { THEME_STORAGE_KEY };
+import { t as THEME_STORAGE_KEY } from "../theme-storage-key-pYlp4aDS.js";
+export { THEME_STORAGE_KEY };

package/dist/layout/theme-storage-key.js

@@ -1,3 +1,6 @@
-export { THEME_STORAGE_KEY } from '../chunk-FMX4GLCQ.js';
-//# sourceMappingURL=theme-storage-key.js.map
+//#region src/layout/theme-storage-key.ts
+const THEME_STORAGE_KEY = "buro-theme";
+//#endregion
+export { THEME_STORAGE_KEY };
+
 //# sourceMappingURL=theme-storage-key.js.map

package/dist/layout/theme-storage-key.js.map

@@ -1 +1 @@
-{"version":3,"sources":[],"names":[],"mappings":"","file":"theme-storage-key.js"}
+{"version":3,"file":"theme-storage-key.js","names":[],"sources":["../../src/layout/theme-storage-key.ts"],"sourcesContent":["/**\n * The ONE localStorage key every theme-aware place in the app must agree on.\n * Exported so nothing re-types the string — two files agreeing on a literal\n * is how they drift.\n *\n * Deliberately its own module: no `'use client'`, no React import, nothing\n * that would pull in `use-theme.ts`'s hook (or the rest of the kit's client\n * component tree). That matters because the consumer that needs this\n * constant outside a hook is a pre-paint bootstrap `<script>` in a Next root\n * `app/layout.tsx` — a Server Component, which cannot itself carry\n * `'use client'`. `examples/next/app/layout.tsx` is that consumer, and after\n * SP9 deleted `apps/playground` it is the only one; a plain-HTML host has the\n * same need but no module graph to satisfy it from, which is why\n * `examples/marketplace-ops/index.html` spells the key as a literal and pins\n * it against this constant in a test instead.\n * Importing from the package's main entry (`@burojs/ui-shadcn`)\n * there fails Next's server/client boundary check, because that entry\n * bundles the whole kit — including many components that call hooks —\n * into one file without a top-level `'use client'` directive (the bundler\n * drops it when merging multiple client modules together — true of tsdown,\n * as it was of tsup). Importing this file\n * directly via the `@burojs/ui-shadcn/theme-storage-key` subpath sidesteps\n * that: it has no hooks, so a Server Component can import the real string\n * value at build/SSR time. `use-theme.ts` re-exports the same constant for\n * everyone else, so there is exactly one literal in the whole codebase.\n */\nexport const THEME_STORAGE_KEY = 'buro-theme';\n"],"mappings":";AA0BA,MAAa,oBAAoB"}