@orbytes/astrolab 0.3.0 → 0.4.0-next.1

package/src/shell/lab-index.ts

@@ -13,8 +13,8 @@
 //      survives a multi-page site.
 //   5. <directory>/responsive.json, through marks.mjs — the hand-set responsive marks. The one
 //      thing here that is ticked rather than derived, because approval cannot be read from code.
-//   6. The stories files themselves — the component they render, the leading comment (summary)
-//      and, through import.meta.glob, the default export's optional `meta.tags`.
+//   6. The stories files themselves, read as text — the component they render, the leading
+//      comment (summary) and the default export's optional `meta.tags`.
 //
 // Classification is by Astrobook `directory` (relative to its `directory` option):
 //   <tier>/<Section>/<Version>/…   tier = first segment; for the tier holding the RESPONSIVE role
@@ -108,17 +108,26 @@ export interface LabIndex {
   live: { file: string; page: string; slot: number; of: number }[];
 }
 
-// Only for the optional `meta` on a story module's default export — Astrobook ignores unknown
-// keys, so `export default { component, meta: { tags: [...] } }` is legal and this is where it is
-// read. Keys are root-relative (`/src/...`); the pattern covers both the current and target trees.
-const storyExports = import.meta.glob("/src/**/*.stories.ts", { eager: true }) as Record<
-  string,
-  { default?: { meta?: { tags?: unknown } } } | undefined
->;
-
-const tagsOf = (moduleFile: string): string[] => {
-  const tags = storyExports[`/${moduleFile}`]?.default?.meta?.tags;
-  return Array.isArray(tags) ? tags.filter((t): t is string => typeof t === "string") : [];
+// The optional `meta.tags` on a story module's default export — Astrobook ignores unknown keys, so
+// `export default { component, meta: { tags: ["cta", "v2"] } }` is legal and this is where it is
+// read.
+//
+// READ AS TEXT, NOT IMPORTED (2026-09-24, ASTROL-12). This used to be an EAGER
+// `import.meta.glob("/src/**/*.stories.ts")`, and importing a stories file imports the component it
+// renders — so every chrome page's module graph held every section, and Astro put every section's
+// scoped stylesheet on every chrome page (18 of them on the lab home). The tags are string
+// literals in the file, so a parse of its text gives the same answer and imports nothing. A tag
+// built at runtime is not seen, which a tag never needs to be.
+const tagsOf = (rootDir: string, moduleFile: string): string[] => {
+  let source = "";
+  try {
+    source = readFileSync(path.join(rootDir, moduleFile), "utf8");
+  } catch {
+    return [];
+  }
+  const list = source.match(/\bmeta\s*:\s*\{[^}]*?\btags\s*:\s*\[([^\]]*)\]/);
+  if (!list) return [];
+  return [...list[1]!.matchAll(/["'`]([^"'`\n]+)["'`]/g)].map((m) => m[1]!);
 };
 
 // First sentence of the leading `//` comment block — the stories files already open with the
@@ -200,7 +209,7 @@ export function buildLabIndex(): LabIndex {
     const liveOn = (componentFile ? mountsByFile.get(componentFile) : undefined) ?? [];
     const primary = liveOn[0];
     const { tier, section, version } = classify(mod.directory);
-    const tags = tagsOf(moduleFile);
+    const tags = tagsOf(rootDir, moduleFile);
     const summary = summaryOf(rootDir, moduleFile);
     const responsive = RESPONSIVE_DIR && moduleFile.startsWith(RESPONSIVE_DIR)
       ? { done: doneMarks.has(moduleFile), approved: approvedMarks.has(moduleFile) }

package/src/ui/components/app.astro

@@ -1,13 +1,11 @@
 ---
 // Vendored from astrobook 0.13.3 (packages/ui/src/components/app.astro) — see
-// ../../core/LICENSE-astrobook. Unchanged apart from the .astro extension on the relative import.
+// ../../core/LICENSE-astrobook.
 //
-// The `/lab` home page: pure chrome, so it renders through ./layout.astro and gets no consumer
-// CSS at all (ruled 2026-09-22 — ../lab.css).
-import Layout from './layout.astro'
+// The `/lab` home page. Divergence: upstream wrapped the `home` component in its layout; since the
+// redesign (2026-09-24) the home component IS the whole document — it renders through the
+// package's chrome shell (../../chrome/Shell.astro) itself, so this file only mounts it.
 import Home from 'virtual:astrobook/components/home.mjs'
 ---
 
-<Layout story={undefined} hasSidebar={true}>
-  <Home />
-</Layout>
+<Home />

package/src/ui/components/theme-script.astro

@@ -18,11 +18,22 @@
 //
 // `is:inline` and no bundling on purpose: this must run before the first paint, or the lab
 // flashes light before turning dark.
+//
+// TWO THEMES SINCE 2026-09-24, one per KEY. The chrome's light/dark and the preview's are
+// separate (decided that day): switching the lab to dark must not switch the site inside the
+// frame. Both documents share an origin and so share localStorage, so the only thing that can
+// keep them apart is the key — the chrome passes `lab-chrome-theme`, and the preview keeps the
+// original `theme-toggle`, so a preview preference stored before the split still applies.
+interface Props {
+  storageKey?: string;
+}
+
+const { storageKey = "theme-toggle" } = Astro.props;
 ---
 
-<script is:inline>
+<script is:inline define:vars={{ storageKey }}>
   (() => {
-    const STORAGE_KEY = "theme-toggle";
+    const STORAGE_KEY = storageKey;
     let current;
 
     const systemTheme = () =>