svelte-docsmith 0.12.0 → 0.12.2

package/dist/buildtime/cli/archive-version.js

@@ -13,7 +13,7 @@ import path from 'node:path';
 import { assertValidVersionId } from '../../core/version.js';
 import { freezeLastUpdated, isInheritedRouteFile, rewriteDocsLinks } from '../archive.js';
 import { ARCHIVE_MARKER, discoverArchives, markerContents } from '../archives.js';
-import { lastCommitDate } from '../git.js';
+import { commitDates } from '../git.js';
 import { docsBaseFrom } from '../paths.js';
 import { isPageFile } from '../vite/pages.js';
 import { CliError } from './error.js';
@@ -79,6 +79,14 @@ export function archiveVersion(options, log) {
                 yield { file, source: path.join(contentDir, path.relative(toDir, file)) };
         }
     }
+    // Read the dates before copying, so the walk sees the docs root as it was
+    // rather than a tree half full of untracked copies. Say so if they could not
+    // be read: an archive is written once and never edited again, so a page that
+    // misses its date here keeps the wrong one for good.
+    const dates = commitDates(contentDir, (reason) => {
+        log(`\n! Could not read commit dates: ${reason}`);
+        log('  Archived pages will keep no last-updated date.\n');
+    });
     copyCurrent(contentDir, toDir);
     fs.writeFileSync(path.join(toDir, ARCHIVE_MARKER), markerContents(id));
     let pages = 0;
@@ -87,12 +95,15 @@ export function archiveVersion(options, log) {
             continue;
         pages++;
         const text = fs.readFileSync(file, 'utf-8');
-        fs.writeFileSync(file, freezeLastUpdated(rewriteDocsLinks(text, { docsBase, versionId: id, archivedIds }), lastCommitDate(source)));
+        fs.writeFileSync(file, freezeLastUpdated(rewriteDocsLinks(text, { docsBase, versionId: id, archivedIds }), dates.get(source)));
     }
     log(`\n✓ Archived the current docs into ${rel(toDir)} (${pages} pages)\n`);
-    log('Links were rewritten to stay inside the archive, and each page kept');
-    log('its real last-updated date. Review the diff, then update');
-    log('docsmith({ versions }) so the archive is served:\n');
+    log('Links were rewritten to stay inside the archive.');
+    // Only claim the dates were kept when the walk actually produced some.
+    if (dates.size)
+        log('Each page kept its real last-updated date.');
+    log('Review the diff, then update docsmith({ versions }) so the archive');
+    log('is served:\n');
     log('  versions: {');
     log("    current: { id: '<new release>', label: '<new release>' },");
     log(`    archived: [{ id: '${id}', label: '${label}' }${archivedIds.size ? ', …' : ''}]`);

package/dist/buildtime/git.d.ts

@@ -1,5 +1,33 @@
-/** Commit day (`YYYY-MM-DD`) a file last changed, or undefined outside a repo. */
-export declare function lastCommitDate(file: string): string | undefined;
+/**
+ * Commit day (`YYYY-MM-DD`) every tracked file under `dir` last changed, keyed by
+ * absolute path. One history walk rather than a `git log` per file: the per-file
+ * form costs a process each, which is the build's largest single expense once a
+ * site has more than a handful of pages.
+ *
+ * `--relative` makes git print paths relative to `dir`, so they join straight
+ * back onto it with no second call to find the repository root. `--no-renames`
+ * makes a rename list both of its paths, which keeps the answer identical to
+ * asking about one file at a time.
+ *
+ * An empty map for a directory outside a repository, or one git could not read.
+ * That is the same "no date" every caller already handles, and it is deliberately
+ * all-or-nothing: a truncated read would date some pages and not others, which
+ * looks like real data and is not.
+ *
+ * Only a truncated read calls `onFail`, because it is the one failure that would
+ * otherwise date some pages and not others. A directory outside a repository, a
+ * missing directory, or a machine without git all yield no dates, which every
+ * caller already handles and which the plugin already reports where it matters.
+ * Reporting is the caller's to do, which is why this takes a callback rather
+ * than writing to the console itself.
+ */
+export declare function commitDates(dir: string, onFail?: (reason: string) => void, 
+/**
+ * Cap on the walk's output. The default is far above any real docs root; it is
+ * a parameter so the truncation path can be exercised without a repository
+ * large enough to produce 256 MB of history.
+ */
+maxBuffer?: number): Map<string, string>;
 /**
  * Release dates keyed by version, read from the commit that introduced each
  * `## <version>` heading in a changelog. Changesets does not write dates, and a

package/dist/buildtime/git.js

@@ -12,14 +12,64 @@
  */
 import { spawnSync } from 'node:child_process';
 import path from 'node:path';
-/** Commit day (`YYYY-MM-DD`) a file last changed, or undefined outside a repo. */
-export function lastCommitDate(file) {
-    const res = spawnSync('git', ['log', '-1', '--format=%cs', '--', file], {
-        cwd: path.dirname(file),
-        encoding: 'utf-8'
-    });
-    const date = res.status === 0 ? res.stdout.trim() : '';
-    return date || undefined;
+/**
+ * Commit day (`YYYY-MM-DD`) every tracked file under `dir` last changed, keyed by
+ * absolute path. One history walk rather than a `git log` per file: the per-file
+ * form costs a process each, which is the build's largest single expense once a
+ * site has more than a handful of pages.
+ *
+ * `--relative` makes git print paths relative to `dir`, so they join straight
+ * back onto it with no second call to find the repository root. `--no-renames`
+ * makes a rename list both of its paths, which keeps the answer identical to
+ * asking about one file at a time.
+ *
+ * An empty map for a directory outside a repository, or one git could not read.
+ * That is the same "no date" every caller already handles, and it is deliberately
+ * all-or-nothing: a truncated read would date some pages and not others, which
+ * looks like real data and is not.
+ *
+ * Only a truncated read calls `onFail`, because it is the one failure that would
+ * otherwise date some pages and not others. A directory outside a repository, a
+ * missing directory, or a machine without git all yield no dates, which every
+ * caller already handles and which the plugin already reports where it matters.
+ * Reporting is the caller's to do, which is why this takes a callback rather
+ * than writing to the console itself.
+ */
+export function commitDates(dir, onFail, 
+/**
+ * Cap on the walk's output. The default is far above any real docs root; it is
+ * a parameter so the truncation path can be exercised without a repository
+ * large enough to produce 256 MB of history.
+ */
+maxBuffer = 256 * 1024 * 1024) {
+    const dates = new Map();
+    const res = spawnSync('git', ['log', '--format=%cs', '--name-only', '--relative', '--no-renames', '--', '.'], 
+    // The 1 MB default would truncate rather than throw on a large history,
+    // which is why the cap is raised and the result checked below.
+    { cwd: dir, encoding: 'utf-8', maxBuffer });
+    // `ENOBUFS` is the output outgrowing maxBuffer, which truncates rather than
+    // throws and is the only failure that could leave a half-filled map. `ENOENT`
+    // (no such directory, or no git installed) and a non-zero status ("not a
+    // repository") both mean no dates at all, which is a state callers expect.
+    if (res.error?.code === 'ENOBUFS') {
+        onFail?.(res.error.message);
+    }
+    if (res.error || res.status !== 0)
+        return dates;
+    let date;
+    for (const line of res.stdout.split('\n')) {
+        if (!line)
+            continue;
+        if (/^\d{4}-\d{2}-\d{2}$/.test(line)) {
+            date = line;
+            continue;
+        }
+        // Newest commit first, so the first date a file appears under is its latest.
+        const file = path.resolve(dir, line);
+        if (date && !dates.has(file))
+            dates.set(file, date);
+    }
+    return dates;
 }
 /**
  * Release dates keyed by version, read from the commit that introduced each

package/dist/buildtime/vite/index.js

@@ -26,6 +26,7 @@ import { docsBaseFrom } from '../paths.js';
 import { isPageFile, readSourcePages, withCommitDates } from './pages.js';
 import { contentIndex, llmsIndex, searchIndex } from './collect.js';
 import { collectReleases } from './releases.js';
+import { commitDates } from '../git.js';
 /**
  * The svelte-docsmith Vite plugin. Add it to `plugins` in `vite.config.ts`:
  *
@@ -70,6 +71,17 @@ function contentIndexPlugin(options) {
     const changelogRoute = options.changelogPath ?? '/changelog';
     const changelogOverrides = path.join(routesDir, changelogRoute);
     const indexOptions = { contentDir, routesDir, versions };
+    // One history walk, reused for the life of the plugin. A build loads this
+    // module once, so it is always fresh there; `dev` reloads it on every page
+    // save, and re-walking each time would cost git a process for dates that
+    // cannot have changed without a commit. The trade is that committing during
+    // `dev` leaves the dates as they were until the server restarts.
+    let dates;
+    const trackedDates = () => (dates ??= commitDates(contentDir, (reason) => {
+        console.warn(`[svelte-docsmith] could not read commit dates under ${contentDir}\n` +
+            `  ${reason}\n` +
+            `  Pages will render without a last-updated date, and sitemap entries without \`lastmod\`.`);
+    }));
     return {
         name: 'docsmith-content',
         enforce: 'pre',
@@ -101,7 +113,7 @@ function contentIndexPlugin(options) {
                 const { pages, exists } = readSourcePages(contentDir);
                 watch(pages);
                 // Only this index has a date field, so only this one pays for git.
-                const docs = contentIndex(withCommitDates(pages), indexOptions);
+                const docs = contentIndex(withCommitDates(pages, trackedDates()), indexOptions);
                 warnAboutDocsRoot(contentDir, exists, docs.length);
                 const resolved = resolveVersions(versions, docsBase, docs);
                 return (`export const docs = ${JSON.stringify(docs, null, 2)};\n` +

package/dist/buildtime/vite/pages.d.ts

@@ -39,18 +39,18 @@ export declare function readSourcePages(contentDir: string): {
  */
 export declare function titleOf(page: SourcePage): string | undefined;
 /**
- * Date each page from the commit that last touched it, skipping the lookup for
- * pages that carry their own `lastUpdated`. Archiving copies every page in one
- * commit, so an archive's pages are written with the date they last really
- * changed and must keep it.
+ * Date each page from `dates`, keyed by absolute path, unless it carries its own
+ * frontmatter `lastUpdated`. Archiving copies every page in one commit, so an
+ * archive's pages are written with the date they last really changed and must
+ * keep it.
  *
- * Deliberately a second pass rather than part of {@link readSourcePages}: it
- * spawns a git process per page, and only the content index has a date field.
- * Folding it into the read would make the search and llms indexes pay for a
- * value neither of them has anywhere to put. For the same reason it skips
- * untitled pages, which no index carries.
+ * Pure: the caller walks git once with {@link commitDates} and hands the result
+ * in. Asking per page cost a process each and was the build's largest single
+ * expense, and doing the walk here would put it behind a function the search and
+ * llms indexes also call, making them pay for a date neither has anywhere to put.
+ * For the same reason this skips untitled pages, which no index carries.
  */
-export declare function withCommitDates(pages: SourcePage[]): SourcePage[];
+export declare function withCommitDates(pages: SourcePage[], dates: Map<string, string>): SourcePage[];
 /**
  * List the absolute paths of every `+page.md`/`+page.svx` under `contentDir`.
  */

package/dist/buildtime/vite/pages.js

@@ -7,7 +7,6 @@
 import fs from 'node:fs';
 import path from 'node:path';
 import { parseFrontmatter } from './frontmatter.js';
-import { lastCommitDate } from '../git.js';
 const PAGE_NAMES = ['+page.md', '+page.svx'];
 /** Whether a filename is a doc page the plugin should index. */
 export function isPageFile(file) {
@@ -40,18 +39,18 @@ export function titleOf(page) {
     return typeof page.frontmatter.title === 'string' ? page.frontmatter.title : undefined;
 }
 /**
- * Date each page from the commit that last touched it, skipping the lookup for
- * pages that carry their own `lastUpdated`. Archiving copies every page in one
- * commit, so an archive's pages are written with the date they last really
- * changed and must keep it.
+ * Date each page from `dates`, keyed by absolute path, unless it carries its own
+ * frontmatter `lastUpdated`. Archiving copies every page in one commit, so an
+ * archive's pages are written with the date they last really changed and must
+ * keep it.
  *
- * Deliberately a second pass rather than part of {@link readSourcePages}: it
- * spawns a git process per page, and only the content index has a date field.
- * Folding it into the read would make the search and llms indexes pay for a
- * value neither of them has anywhere to put. For the same reason it skips
- * untitled pages, which no index carries.
+ * Pure: the caller walks git once with {@link commitDates} and hands the result
+ * in. Asking per page cost a process each and was the build's largest single
+ * expense, and doing the walk here would put it behind a function the search and
+ * llms indexes also call, making them pay for a date neither has anywhere to put.
+ * For the same reason this skips untitled pages, which no index carries.
  */
-export function withCommitDates(pages) {
+export function withCommitDates(pages, dates) {
     return pages.map((page) => {
         if (titleOf(page) === undefined)
             return page;
@@ -59,7 +58,7 @@ export function withCommitDates(pages) {
             ...page,
             lastUpdated: typeof page.frontmatter.lastUpdated === 'string'
                 ? page.frontmatter.lastUpdated
-                : lastCommitDate(page.file)
+                : dates.get(page.file)
         };
     });
 }

package/dist/components/markdown/pre.svelte

@@ -98,7 +98,7 @@
 		{/if}
 
 		<pre
-			class="not-prose shiki max-h-[32rem] flex shrink"
+			class="docsmith-code not-prose shiki max-h-[32rem] flex shrink"
 			class:docsmith-line-numbers={lineNumbers}
 			style={lineNumbers && startLine !== 1 ? `--docsmith-line-start: ${startLine - 1}` : undefined}
 			use:clipboard.readText>
@@ -113,8 +113,17 @@
 	 * published package, where the consumer's Tailwind theme context isn't
 	 * available to resolve @apply (Tailwind v4 compiles scoped styles in
 	 * isolation).
+	 *
+	 * Shiki's markup arrives through `{@html}`, so Svelte cannot scope these for
+	 * us and they have to be global. Every one is therefore anchored on
+	 * `pre.docsmith-code`, the class this component puts on its own element.
+	 * Anchoring on the bare element instead would restyle every code block on
+	 * the page, including ones this component never rendered — and since a
+	 * route's CSS only arrives when that route loads (SvelteKit preloads on
+	 * link hover), the restyle would land mid-session and shift the layout
+	 * under the pointer.
 	 */
-	:global(pre code) {
+	:global(pre.docsmith-code code) {
 		display: block;
 		flex-grow: 1;
 		height: 100%;
@@ -122,7 +131,7 @@
 		padding-block: 1rem;
 	}
 
-	:global(pre span.line) {
+	:global(pre.docsmith-code span.line) {
 		display: inline-block;
 		width: 100%;
 		padding-inline: 1rem;
@@ -149,15 +158,15 @@
 	   A CSS counter on Shiki's existing per-line spans, so numbering adds no DOM
 	   and stays out of the text the copy button reads. `--docsmith-line-start`
 	   offsets the counter for a snippet lifted out of a larger file. */
-	:global(pre.docsmith-line-numbers code) {
+	:global(pre.docsmith-code.docsmith-line-numbers code) {
 		counter-reset: docsmith-line var(--docsmith-line-start, 0);
 	}
-	:global(pre.docsmith-line-numbers span.line) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line) {
 		counter-increment: docsmith-line;
 		position: relative;
 		padding-inline-start: 3.2rem;
 	}
-	:global(pre.docsmith-line-numbers span.line::before) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line::before) {
 		content: counter(docsmith-line);
 		position: absolute;
 		left: 0;
@@ -169,19 +178,19 @@
 		user-select: none;
 	}
 	/* The diff gutter glyph would collide with the number, so shift it over. */
-	:global(pre.docsmith-line-numbers span.line.diff::before) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line.diff::before) {
 		content: counter(docsmith-line);
 	}
-	:global(pre.docsmith-line-numbers span.line.diff::after) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line.diff::after) {
 		position: absolute;
 		left: 2.7rem;
 		font-weight: 600;
 	}
-	:global(pre.docsmith-line-numbers span.line.diff.add::after) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line.diff.add::after) {
 		content: '+';
 		color: oklch(0.6 0.15 150);
 	}
-	:global(pre.docsmith-line-numbers span.line.diff.remove::after) {
+	:global(pre.docsmith-code.docsmith-line-numbers span.line.diff.remove::after) {
 		content: '−';
 		color: oklch(0.58 0.19 25);
 	}
@@ -193,76 +202,76 @@
 	   the code background via color-mix. */
 
 	/* --- Line highlight (// [!code highlight] and {1,3} meta) --- */
-	:global(pre span.line.highlighted) {
+	:global(pre.docsmith-code span.line.highlighted) {
 		background: color-mix(in oklch, var(--primary) 12%, transparent);
 	}
-	:global(.dark pre span.line.highlighted) {
+	:global(.dark pre.docsmith-code span.line.highlighted) {
 		background: color-mix(in oklch, var(--primary) 20%, transparent);
 	}
 
 	/* --- Diff (// [!code ++] / [!code --]) with +/- gutter glyphs --- */
-	:global(pre span.line.diff) {
+	:global(pre.docsmith-code span.line.diff) {
 		position: relative;
 	}
-	:global(pre span.line.diff.add) {
+	:global(pre.docsmith-code span.line.diff.add) {
 		background: color-mix(in oklch, oklch(0.7 0.16 150) 15%, transparent);
 	}
-	:global(pre span.line.diff.remove) {
+	:global(pre.docsmith-code span.line.diff.remove) {
 		background: color-mix(in oklch, oklch(0.62 0.2 25) 14%, transparent);
 	}
-	:global(.dark pre span.line.diff.add) {
+	:global(.dark pre.docsmith-code span.line.diff.add) {
 		background: color-mix(in oklch, oklch(0.7 0.16 150) 22%, transparent);
 	}
-	:global(.dark pre span.line.diff.remove) {
+	:global(.dark pre.docsmith-code span.line.diff.remove) {
 		background: color-mix(in oklch, oklch(0.62 0.2 25) 22%, transparent);
 	}
-	:global(pre span.line.diff::before) {
+	:global(pre.docsmith-code span.line.diff::before) {
 		position: absolute;
 		left: 0.45rem;
 		font-weight: 600;
 	}
-	:global(pre span.line.diff.add::before) {
+	:global(pre.docsmith-code span.line.diff.add::before) {
 		content: '+';
 		color: oklch(0.6 0.15 150);
 	}
-	:global(pre span.line.diff.remove::before) {
+	:global(pre.docsmith-code span.line.diff.remove::before) {
 		content: '−';
 		color: oklch(0.58 0.19 25);
 	}
-	:global(.dark pre span.line.diff.add::before) {
+	:global(.dark pre.docsmith-code span.line.diff.add::before) {
 		color: oklch(0.78 0.17 150);
 	}
-	:global(.dark pre span.line.diff.remove::before) {
+	:global(.dark pre.docsmith-code span.line.diff.remove::before) {
 		color: oklch(0.72 0.18 25);
 	}
 
 	/* --- Error / warning severity (// [!code error] / [!code warning]).
 	   No gutter glyph, so they stay distinct from the +/- diff lines. --- */
-	:global(pre span.line.highlighted.error) {
+	:global(pre.docsmith-code span.line.highlighted.error) {
 		background: color-mix(in oklch, oklch(0.62 0.2 25) 18%, transparent);
 	}
-	:global(pre span.line.highlighted.warning) {
+	:global(pre.docsmith-code span.line.highlighted.warning) {
 		background: color-mix(in oklch, oklch(0.8 0.13 85) 22%, transparent);
 	}
-	:global(.dark pre span.line.highlighted.error) {
+	:global(.dark pre.docsmith-code span.line.highlighted.error) {
 		background: color-mix(in oklch, oklch(0.62 0.2 25) 26%, transparent);
 	}
-	:global(.dark pre span.line.highlighted.warning) {
+	:global(.dark pre.docsmith-code span.line.highlighted.warning) {
 		background: color-mix(in oklch, oklch(0.8 0.13 85) 20%, transparent);
 	}
 
 	/* --- Focus (// [!code focus]): dim the other lines and restore on hover.
 	   A clean opacity fade reads calmer than a muddy blur. `:has` recreates
 	   Shiki's stripped container flag from the line classes alone. --- */
-	:global(pre code:has(span.line.focused) span.line:not(.focused)) {
+	:global(pre.docsmith-code code:has(span.line.focused) span.line:not(.focused)) {
 		opacity: 0.42;
 		transition: opacity 0.25s ease;
 	}
-	:global(pre:hover code:has(span.line.focused) span.line:not(.focused)) {
+	:global(pre.docsmith-code:hover code:has(span.line.focused) span.line:not(.focused)) {
 		opacity: 1;
 	}
 	@media (prefers-reduced-motion: reduce) {
-		:global(pre code:has(span.line.focused) span.line:not(.focused)) {
+		:global(pre.docsmith-code code:has(span.line.focused) span.line:not(.focused)) {
 			transition: none;
 		}
 	}
@@ -273,11 +282,11 @@
 	   inspectable; the popup is a hidden sibling revealed on hover. `unclipPopups`
 	   then promotes it to fixed positioning so the code block's scrolling does not
 	   clip it — see the comment there. */
-	:global(pre .twoslash-hover) {
+	:global(pre.docsmith-code .twoslash-hover) {
 		position: relative;
 		border-bottom: 1px dotted color-mix(in oklch, var(--muted-foreground) 55%, transparent);
 	}
-	:global(pre .twoslash-popup-container) {
+	:global(pre.docsmith-code .twoslash-popup-container) {
 		position: absolute;
 		z-index: 40;
 		display: none;
@@ -298,11 +307,11 @@
 		font-size: 0.85em;
 		line-height: 1.5;
 	}
-	:global(pre .twoslash-hover:hover .twoslash-popup-container) {
+	:global(pre.docsmith-code .twoslash-hover:hover .twoslash-popup-container) {
 		display: block;
 	}
 	/* The signature keeps Shiki's own colours and monospace. */
-	:global(pre .twoslash-popup-code) {
+	:global(pre.docsmith-code .twoslash-popup-code) {
 		display: block;
 		font-family: var(--font-mono, ui-monospace, monospace);
 		white-space: pre-wrap;
@@ -311,7 +320,7 @@
 	/* Prose, by contrast, is prose. Inside a <pre> it would otherwise inherit
 	   monospace and whatever token colour the hovered span happened to carry,
 	   which reads as more code rather than an explanation of it. */
-	:global(pre .twoslash-popup-docs) {
+	:global(pre.docsmith-code .twoslash-popup-docs) {
 		/* The dark-theme swap repaints every span inside `.shiki` with
 		   `--shiki-dark`, which these spans inherit from whichever token was
 		   hovered — so docs took on the colour of the word above them. Redefining
@@ -330,20 +339,20 @@
 
 	/* Each @param is its own line: the tags are inline spans, so without this
 	   they run together into one paragraph. */
-	:global(pre .twoslash-popup-docs-tags) {
+	:global(pre.docsmith-code .twoslash-popup-docs-tags) {
 		display: flex;
 		flex-direction: column;
 		gap: 0.35rem;
 	}
-	:global(pre .twoslash-popup-docs-tag) {
+	:global(pre.docsmith-code .twoslash-popup-docs-tag) {
 		display: block;
 	}
-	:global(pre .twoslash-popup-docs-tag-value) {
+	:global(pre.docsmith-code .twoslash-popup-docs-tag-value) {
 		--shiki-dark: var(--muted-foreground);
 		color: var(--muted-foreground);
 	}
 	/* And the tag name needs a gap, or it reads as "@paramcallbackfn". */
-	:global(pre .twoslash-popup-docs-tag-name) {
+	:global(pre.docsmith-code .twoslash-popup-docs-tag-name) {
 		--shiki-dark: var(--primary);
 		margin-right: 0.4em;
 		font-family: var(--font-mono, ui-monospace, monospace);
@@ -351,18 +360,18 @@
 		color: var(--primary);
 	}
 	/* A snippet that deliberately shows an error (// @errors:) marks the line. */
-	:global(pre .twoslash-error) {
+	:global(pre.docsmith-code .twoslash-error) {
 		background: color-mix(in oklch, oklch(0.62 0.2 25) 14%, transparent);
 	}
 
 	/* --- Word highlight (// [!code word:name]): a primary-tinted inline pill --- */
-	:global(pre .highlighted-word) {
+	:global(pre.docsmith-code .highlighted-word) {
 		border-radius: 0.3rem;
 		padding: 0.1rem 0.3rem;
 		background: color-mix(in oklch, var(--primary) 16%, transparent);
 		box-shadow: 0 0 0 1px color-mix(in oklch, var(--primary) 35%, transparent);
 	}
-	:global(.dark pre .highlighted-word) {
+	:global(.dark pre.docsmith-code .highlighted-word) {
 		background: color-mix(in oklch, var(--primary) 24%, transparent);
 	}
 </style>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "svelte-docsmith",
-  "version": "0.12.0",
+  "version": "0.12.2",
   "description": "A framework for building beautiful documentation sites with Svelte.",
   "author": {
     "name": "George Daskalakis",