stack-site-builder 1.17.0 → 1.17.1

package/CHANGELOG.md

@@ -11,6 +11,25 @@ content schema, while a consuming site supplies only content, taxonomy data and
 config. Sites track the theme with `pnpm up stack-site-builder`, so each release
 here is a plain version bump they pull in.
 
+## [1.17.1] - 2026-07-22
+
+### Fixed
+
+- **Mermaid never rendered on npm-consuming sites' dev server** — the loader
+  imported the package default (`mermaid.core.mjs`), whose bare CJS
+  dependencies (dayjs, …) are served without interop when the import chain
+  starts inside `node_modules`, killing the whole loader module with a
+  SyntaxError. It now imports the self-contained
+  `mermaid/dist/mermaid.esm.min.mjs` bundle, which loads identically in dev
+  and build. (The theme's own playground never hit this — its workspace
+  symlink resolves outside `node_modules`, so Vite prebundled mermaid.)
+
+- **Course → slide-deck links matched nothing** — a course's `slides`
+  frontmatter lists locale-less deck slugs, but the detail page compared
+  them against raw collection ids (`ko/<deck>/index`), so the chips never
+  rendered and would have linked to the wrong path. Decks are now resolved
+  per locale via the slides helpers.
+
 ## [1.17.0] - 2026-07-22
 
 ### Changed
@@ -225,6 +244,7 @@ catalog sites from a thin content-only repository.
 - **Standalone development setup** — a devcontainer and a minimal `playground/`
   consuming site for developing and previewing the theme on its own.
 
+[1.17.1]: https://github.com/CodeCompose7/stack-site-builder/compare/v1.17.0...v1.17.1
 [1.17.0]: https://github.com/CodeCompose7/stack-site-builder/compare/v1.16.0...v1.17.0
 [1.16.0]: https://github.com/CodeCompose7/stack-site-builder/compare/v1.15.0...v1.16.0
 [1.15.0]: https://github.com/CodeCompose7/stack-site-builder/compare/v1.14.0...v1.15.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "stack-site-builder",
   "type": "module",
-  "version": "1.17.0",
+  "version": "1.17.1",
   "license": "MIT",
   "description": "The engine behind the awesome-*-stack catalog sites: an Astro theme with the catalog/concepts/articles/slides/samples routes, components, styles and markdown pipeline. Sites provide content, taxonomy data and config.",
   "repository": {

package/src/components/CourseDetail.astro

@@ -1,7 +1,8 @@
 ---
-import { render, getCollection } from 'astro:content';
+import { render } from 'astro:content';
 import { getRelativeLocaleUrl } from 'astro:i18n';
 import { getCourses, courseSlugOf, type CourseEntry } from '../lib/courses';
+import { getDecks, deckSlugOf } from '../lib/slides';
 import { inlineMd } from '../lib/inline-md';
 import { Image } from 'astro:assets';
 import { useTranslations, type Lang } from '../i18n/ui';
@@ -33,14 +34,14 @@ const relatedCourses = data.related
   .map((sl) => courseBySlug.get(sl))
   .filter(Boolean) as CourseEntry[];
 
-// Decks in the `slides` collection that belong to this course. Only linked when
-// the slides section is enabled (otherwise its routes don't exist) and the deck
-// id actually resolves — a typo just drops the chip instead of a dead link.
-const slideDecks = sectionEnabled('slides') && data.slides.length > 0
-  ? (await getCollection('slides')).filter(
-      (d) => data.slides.includes(d.id) && !d.data.draft,
-    )
-  : [];
+// Decks in the `slides` collection that belong to this course, matched by
+// their locale-less slug (what the frontmatter lists). Only linked when the
+// slides section is enabled (otherwise its routes don't exist) and the slug
+// actually resolves — a typo just drops the chip instead of a dead link.
+const slideDecks =
+  sectionEnabled('slides') && data.slides.length > 0
+    ? (await getDecks(lang)).filter((d) => data.slides.includes(deckSlugOf(d)))
+    : [];
 
 // Breadcrumb: All courses › category › subcategory… (each segment linked).
 const crumbs = [
@@ -84,7 +85,7 @@ const crumbs = [
         </span>
         {slideDecks.map((d) => (
           <a
-            href={getRelativeLocaleUrl(lang, `slides/${d.id}/`)}
+            href={getRelativeLocaleUrl(lang, `slides/${deckSlugOf(d)}/`)}
             class="rounded-full border border-[var(--aas-border)] bg-[var(--aas-panel)] px-3 py-1 text-sm text-[var(--aas-text)] no-underline hover:bg-[var(--aas-tint)]"
           >
             {d.data.title}

package/src/components/MermaidLoader.astro

@@ -5,7 +5,15 @@
 ---
 
 <script>
-  import mermaid from 'mermaid';
+  // The self-contained browser bundle, NOT the package default: the default
+  // entry (mermaid.core.mjs) keeps dayjs/d3 as bare CJS imports, which break
+  // with a "does not provide an export named 'default'" SyntaxError in a
+  // CONSUMING site's dev server — the theme lives in node_modules there, so
+  // Vite serves the import chain raw without CJS interop. The esm.min bundle
+  // inlines every dependency (relative-chunk imports only), so it loads the
+  // same in dev and build.
+  // @ts-expect-error — the bundled build ships no type mapping; same API.
+  import mermaid from 'mermaid/dist/mermaid.esm.min.mjs';
   import { initOnReady } from '../lib/reinit';
 
   // Read the live site palette so Mermaid matches the current theme exactly.