@rtorcato/repo-tooling 3.2.1 → 3.2.2

package/dist/cli/generators/docs-site.js

@@ -1,8 +1,22 @@
 import path from 'node:path';
 import fs from 'fs-extra';
+import selfPackageJson from '../../../package.json' with { type: 'json' };
 import { copyPreset, PRESETS } from '../utils/copy-preset.js';
 import { buildBadgeRow, parseRepository } from './badges.js';
 import { inferSubpathsFromExports } from './treeshake.js';
+/**
+ * What a scaffolded docs site should depend on for *this* CLI — read from the
+ * running version rather than written down, because a literal here goes stale
+ * silently. It had drifted to `^2.47.0`, two majors behind, so every site
+ * scaffolded since was handed a pre-rename version predating the peer-dependency
+ * split.
+ *
+ * The floor is the exact running version, not `^<major>.0.0`: the config being
+ * generated is the one this version emits, and claiming compatibility back to
+ * the start of the major would be the same over-wide-range problem doctor's
+ * `Config schema versions` check exists to catch (#330).
+ */
+const SELF_RANGE = `^${selfPackageJson.version}`;
 /**
  * Docs-site (Docusaurus) generator — the Phase 2 counterpart to the shared
  * assets shipped in #54. Scaffolds a working Docusaurus site under `apps/docs`,
@@ -179,8 +193,12 @@ ${typedocPlugins}    [
       ],
       copyright: \`Copyright © \${new Date().getFullYear()} ${meta.title}. Built with Docusaurus.\`,
     },
+    // \`theme\` is the LIGHT-mode Prism theme and \`darkTheme\` the dark one. Both
+    // were vsDark here, which is why the shared stylesheet had to pin fenced
+    // blocks dark in light mode too (#324). Keep this pairing and the CSS in
+    // step — vsDark tokens on a light surface are unreadable.
     prism: {
-      theme: prismThemes.vsDark,
+      theme: prismThemes.vsLight,
       darkTheme: prismThemes.vsDark,
       additionalLanguages: ['bash', 'json', 'typescript'],
     },
@@ -222,7 +240,7 @@ const TSCONFIG = `// Improves IDE type-checking; not used by \`docusaurus start/
 `;
 function customCss(accent) {
     // Import the shared tokens, then override only the accent (per #54's model).
-    return `/* Site theme: shared @rtorcato tokens + this project's accent. */
+    return `/* Site theme: the shared design tokens + this project's accent. */
 @import "./_jt-tokens.css";
 
 :root {
@@ -239,7 +257,7 @@ function customCss(accent) {
 function docsPackageJson(meta, typedoc) {
     const typedocDevDeps = typedoc
         ? {
-            '@rtorcato/repo-tooling': '^2.47.0',
+            '@rtorcato/repo-tooling': SELF_RANGE,
             'docusaurus-plugin-typedoc': '^1.4.0',
             typedoc: '^0.28.0',
             'typedoc-plugin-markdown': '^4.9.0',
@@ -278,7 +296,7 @@ function docsPackageJson(meta, typedoc) {
             '@docusaurus/tsconfig': '^3.8.1',
             '@docusaurus/types': '^3.10.2',
             '@playwright/test': '^1.49.0',
-            '@rtorcato/repo-tooling': '^2.47.0',
+            '@rtorcato/repo-tooling': SELF_RANGE,
             '@types/react': '^19.0.0',
             typescript: '~5.6.3',
             ...typedocDevDeps,

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@rtorcato/repo-tooling",
-	"version": "3.2.1",
+	"version": "3.2.2",
 	"description": "One CLI to scaffold, audit and fix your repo's whole toolchain — linting, tests, commits, releases & CI.",
 	"type": "module",
 	"keywords": [
@@ -277,7 +277,7 @@
 		"vitest": "^4.1.10"
 	},
 	"peerDependencies": {
-		"@biomejs/biome": "^2.0.0",
+		"@biomejs/biome": "^2.5.0",
 		"@commitlint/cli": "^20.0.0 || ^21.0.0",
 		"@commitlint/config-conventional": "^21.2.0",
 		"@commitlint/types": "^21.2.0",

package/tooling/docusaurus/theme.css

@@ -185,10 +185,15 @@ body,
 }
 
 /* ---------- Code ----------
-   Prism is vsDark in both light & dark mode (to match the navy aesthetic),
-   so fenced code blocks must stay dark in BOTH themes — otherwise the pale
-   vsDark tokens wash out on a light background. Inline code (the `code` pills)
-   keeps the themed --ifm-code-background and stays readable. */
+   Every surface and text colour here comes from the theme tokens, which already
+   flip between light and dark — the values that used to be hardcoded (#0c111b,
+   #dfe5ee, #94a1b4) were simply the dark side of tokens that existed all along.
+
+   This pairs with `prism.theme: vsLight` / `prism.darkTheme: vsDark` in
+   docusaurus.config.ts. The two must move together (#324): vsDark tokens on a
+   light surface are pale and unreadable, which is why the background was pinned
+   dark in both modes in the first place. If a fenced block still renders dark in
+   light mode, that config is the thing to check. */
 code {
 	background: var(--jt-code-bg);
 	border: 1px solid var(--jt-border);
@@ -202,23 +207,30 @@ div[class*="codeBlockContainer"],
 pre[class*="language-"] {
 	border: 1px solid var(--jt-border);
 	border-radius: 12px;
-	background: #0c111b !important;
+	/* !important beats the inline background the Prism theme sets on the <pre>. */
+	background: var(--jt-code-bg) !important;
 }
 .theme-code-block code,
 pre[class*="language-"] code {
 	background: transparent !important;
 	border: none !important;
-	color: #dfe5ee;
+	/* Base colour for anything Prism does not tokenise. */
+	color: var(--jt-text);
 }
 div[class*="codeBlockTitle"] {
-	background: #0a0e16 !important;
-	color: #94a1b4 !important;
+	background: var(--jt-surface2) !important;
+	color: var(--jt-muted) !important;
 	border-bottom: 1px solid var(--jt-border);
 }
+/* In dark the title sits a shade *below* the block; in light there is no token
+   darker than --jt-code-bg, so the bottom border does the separating instead. */
+[data-theme="dark"] div[class*="codeBlockTitle"] {
+	background: var(--jt-bg) !important;
+}
 [data-theme="light"] .theme-code-block,
 [data-theme="light"] div[class*="codeBlockContainer"],
 [data-theme="light"] pre[class*="language-"] {
-	border-color: rgba(12, 18, 28, 0.16);
+	border-color: var(--jt-border2);
 	box-shadow: 0 8px 24px -18px rgba(12, 18, 28, 0.5);
 }