@peaceroad/markdown-it-renderer-fence 0.4.1 → 0.5.0

package/README.md

@@ -1,177 +1,500 @@
 # p7d-markdown-it-renderer-fence
 
-In code blocks, the `<samp>` tag is used with the language keywords `samp`, `shell`, and `console`.
+A `markdown-it` plugin for code block rendering and enhancements.
 
-To add specific styles to code blocks and display line numbers in code blocks, enclose each line in a span element and set CSS.
+Default is `markup` mode. Custom Highlight API mode is available as an advanced/experimental path.
 
-## Use
+## Install
 
-It is assumed that you will use  highlight.js and markdown-it-attrs together. It will probably work without them though.
+```bash
+npm i @peaceroad/markdown-it-renderer-fence markdown-it markdown-it-attrs
+```
 
-```js
-import mdit from 'markdown-it'
-import mditAttrs from 'markdown-it-attrs'
-import highlightjs from 'highlihgtjs'
-import mditRendererFence from '@peaceroad/markdown-it-renderer-fence'
+If you use syntax highlighting, install a highlighter too (for example `highlight.js` or `shiki`).
 
-const md = mdit({
-             langPrefix: 'language-',
-             highlight: (str, lang) => {
-               if (lang && highlightjs.getLanguage(lang)) {
-                 try {
-                    return highlightjs.highlight(str, { language: lang }).value
-                 } catch (__) {}
-               }
-             return md.utils.escapeHtml(str)
-             }
-           }).use(mditAttrs).use(mditRendererFence)
+## Entry Points
 
-const htmlCont = md.render('...')
-```
+- `@peaceroad/markdown-it-renderer-fence`  
+  Dispatcher entry (`highlightRenderer` selects mode).
+- `@peaceroad/markdown-it-renderer-fence/markup-highlight`  
+  Markup-focused entry.
+- `@peaceroad/markdown-it-renderer-fence/custom-highlight`  
+  API-mode entry + runtime/payload helpers.
+- `@peaceroad/markdown-it-renderer-fence/custom-highlight-runtime`  
+  Runtime-only entry (`applyCustomHighlights` / `observeCustomHighlights` / `clearCustomHighlights`).
 
-It is also intended to be used in conjunction with @peaceroad/markdown-it-figure-with-p-caption.
+## Markup Mode (Default)
 
-## Code block to samp block
+### Quick Start
 
-~~~
-[Markdown]
-```samp
-$ pwd
-/home/User
+Dispatcher entry:
+
+```js
+import MarkdownIt from 'markdown-it'
+import markdownItAttrs from 'markdown-it-attrs'
+import hljs from 'highlight.js'
+import rendererFence from '@peaceroad/markdown-it-renderer-fence'
+// Markup-only entry (skips dispatcher/API branch):
+// import rendererFence from '@peaceroad/markdown-it-renderer-fence/markup-highlight'
+
+const md = MarkdownIt({
+  html: true,
+  langPrefix: 'language-',
+  highlight: (code, lang) => {
+    if (lang && hljs.getLanguage(lang)) {
+      try {
+        return hljs.highlight(code, { language: lang }).value
+      } catch (e) {}
+    }
+    return md.utils.escapeHtml(code)
+  },
+})
+  .use(markdownItAttrs)
+  .use(rendererFence) // defaults to markup; direct markup entry can be leaner
 ```
-[HTML]
-<pre><samp>$ pwd
-/home/User
-</samp></pre>
 
+### Markup with Shiki
 
-[Markdown]
-```shell
-$ pwd
-/home/User
+Use the markup-only entry and provide `md.options.highlight` with Shiki.
+For production/blog builds, pre-scan markdown and preload only used languages.
+
+```js
+import MarkdownIt from 'markdown-it'
+import markdownItAttrs from 'markdown-it-attrs'
+import { createHighlighter } from 'shiki'
+import rendererFence from '@peaceroad/markdown-it-renderer-fence/markup-highlight'
+import fs from 'node:fs'
+import path from 'node:path'
+
+const fenceInfoReg = /^```([^\s`{]+)/gm
+const collectFenceLangs = (markdown) => {
+  const out = new Set()
+  if (!markdown) return out
+  let m
+  while ((m = fenceInfoReg.exec(markdown)) !== null) {
+    const lang = String(m[1] || '').trim().toLowerCase()
+    if (lang) out.add(lang)
+  }
+  return out
+}
+
+// Example: scan markdown source(s) before highlighter creation
+const markdown = fs.readFileSync(path.join(process.cwd(), 'article.md'), 'utf8')
+const langs = Array.from(collectFenceLangs(markdown))
+langs.push('text') // safe fallback
+
+const highlighter = await createHighlighter({
+  themes: ['github-light'],
+  langs, // preload grammars; Shiki does not auto-detect language
+})
+
+const md = MarkdownIt({
+  html: true,
+  langPrefix: 'language-',
+  highlight: (code, lang) => {
+    const targetLang = lang || 'text'
+    try {
+      return highlighter.codeToHtml(code, { lang: targetLang, theme: 'github-light' })
+    } catch (e) {
+      // when lang grammar is not loaded (or invalid), keep output safe
+      return md.utils.escapeHtml(code)
+    }
+  },
+})
+  .use(markdownItAttrs)
+  .use(rendererFence)
 ```
-[HTML]
-<pre><samp class="language-shell"><span class="hljs-meta prompt_">$ </span><span class="language-bash"><span class="hljs-built_in">pwd</span></span>
-/home/User
-</samp></pre>
 
+Note:
+
+- For small projects, a fixed list like `['javascript', 'typescript', 'json', 'text']` is also fine.
+- If Shiki grammar for a language is not loaded, `codeToHtml` can fail.
+- In markup mode, handle this in your `highlight` callback (for example fallback to escaped plain text as above).
 
-[Markdown]
-```console
+### Main Features
+
+- `samp` rendering for `samp`, `shell`, `console` languages.
+- line number wrapping via `start` / `data-pre-start`.
+- emphasized lines via `em-lines` / `emphasize-lines`.
+- optional line-end spacer via `lineEndSpanThreshold`.
+- optional pre-wrap support via `wrap` / `pre-wrap`.
+- comment line markers via `comment-mark`.
+
+### Fence Attribute Examples
+
+Simplified HTML below focuses on renderer-fence structure (not full highlighter token spans).
+
+`samp` conversion:
+
+~~~md
+```shell
 $ pwd
-/home/User
 ```
-[HTML]
-<pre><samp class="language-console"><span class="hljs-meta prompt_">$ </span><span class="language-bash"><span class="hljs-built_in">pwd</span></span>
-/home/User
-</samp></pre>
 ~~~
 
+```html
+<pre><samp class="language-shell">$ pwd
+</samp></pre>
+```
 
-## Add span elements to display line number.
-
-Add `start` or `data-pre-start` attribute by adding attributes used markdown-it-attrs.
-Line numbering is enabled only when `start` is a non-negative integer (`0`, `1`, `2`, ...).
+Line numbers:
 
 ~~~md
 ```js {start="1"}
-import mdit from 'markdonw-it'
-const md = mdit()
-md.render('Nyaan')
+const a = 1
+console.log(a)
 ```
 ~~~
 
-~~~html
-<pre><code class="language-js" data-pre-start="1" style="counter-set:pre-line-number 1;"><span class="pre-line"><span class="hljs-keyword">import</span> mdit <span class="hljs-keyword">from</span> <span class="hljs-string">&#x27;markdonw-it&#x27;</span></span>
-<span class="pre-line"><span class="hljs-keyword">const</span> md = <span class="hljs-title function_">mdit</span>()</span>
-<span class="pre-line">md.<span class="hljs-title function_">render</span>(<span class="hljs-string">&#x27;Nyaan&#x27;</span>)</span>
+```html
+<pre><code class="language-js" data-pre-start="1" style="counter-set:pre-line-number 1;">
+<span class="pre-line">const a = 1</span>
+<span class="pre-line">console.log(a)</span>
 </code></pre>
-~~~
-
-CSS example: <https://codepen.io/peaceroad/pen/qBGpYGK>
-
-If `start` is empty or not a non-negative integer (for example `start=""`, `start="abc"`, `start="1.5"`), the attribute is kept as `data-pre-start` but line-number wrapping/counter style is not enabled.
-
-## Add span elements to add background color to the row ranges.
+```
 
-Add `em-lines` or `emphasize-lines` attribute by adding attributes used markdown-it-attrs.
-Open-ended ranges are supported: `-5` (1..5), `3-` (3..last), `-` (all).
+Emphasis:
 
 ~~~md
-``` {em-lines="2,4-5"}
-1
-2
-3
-4
-5
-6
+```js {em-lines="2,4-5"}
+line1
+line2
+line3
+line4
+line5
 ```
 ~~~
 
-~~~html
-[HTML]
-<pre><code data-pre-emphasis="2,4-5">1
-<span class="pre-lines-emphasis">2
-</span>3
-<span class="pre-lines-emphasis">4
-5
-</span>6
+```html
+<pre><code class="language-js" data-pre-emphasis="2,4-5">line1
+<span class="pre-lines-emphasis">line2</span>
+line3
+<span class="pre-lines-emphasis">line4
+line5</span>
 </code></pre>
-~~~
-
-## Enable pre-wrap for code blocks
+```
 
-Add `wrap` or `pre-wrap` attribute (optionally `="true"`) by adding attributes used markdown-it-attrs.
+Wrap:
 
 ~~~md
 ```js {wrap}
-const longLine = 'This line is long but wraps.'
+const veryLongLine = '...'
 ```
 ~~~
 
-~~~html
-<pre data-pre-wrap="true" style="white-space: pre-wrap; overflow-wrap: anywhere;"><code class="language-js">const longLine = 'This line is long but wraps.'
+```html
+<pre data-pre-wrap="true" style="white-space: pre-wrap; overflow-wrap: anywhere;">
+<code class="language-js">const veryLongLine = '...'
 </code></pre>
-~~~
-
-When `setPreWrapStyle` is set to false, only `data-pre-wrap="true"` is added and the inline style is omitted.
-
-## Mark comment lines in code blocks
+```
 
-Add `comment-line` attribute to mark comment lines. Lines that start with the given marker (after leading whitespace) are wrapped with `<span class="pre-comment-line">`.
+Comment line marker:
 
 ~~~md
-```samp {comment-line="#"}
+```samp {comment-mark="#"}
 # comment
 echo 1
 ```
 ~~~
 
-~~~html
-<pre><samp data-pre-comment-line="#"><span class="pre-comment-line"># comment</span>
+```html
+<pre><samp data-pre-comment-mark="#" class="language-samp">
+<span class="pre-line-comment"># comment</span>
 echo 1
 </samp></pre>
-~~~
+```
+
+### Markup Notes
 
-Note: this feature relies on line splitting and is disabled when `useHighlightPre` is true and `<pre><code>` is provided by the highlighter.
-If a highlighter changes logical line count (for example by injecting extra lines), comment-line marking is skipped to avoid wrong line mapping.
-CRLF/LF mixed newlines are supported for logical line-count checks.
+- `useHighlightPre: true` keeps highlighter-provided `<pre><code>` when present.
+- In that passthrough path, line-splitting features are intentionally disabled:
+  - line numbers
+  - `em-lines`
+  - line-end spacer
+  - `comment-mark`
+  - `samp` conversion
 
+### Markup Options
 
-## Options
+- `attrsOrder` (default: `['class', 'id', 'data-*', 'style']`): output attribute order (`data-*` wildcard supported).
+- `setHighlight` (default: `true`): call `md.options.highlight` when available.
+- `setLineNumber` (default: `true`): enable line wrapper spans when `start` is valid.
+- `setEmphasizeLines` (default: `true`): enable `em-lines` / `emphasize-lines`.
+- `lineEndSpanThreshold` (default: `0`): append line-end spacer span when visual width threshold is met.
+- `setLineEndSpan`: alias of `lineEndSpanThreshold`.
+- `lineEndSpanClass` (default: `'pre-lineend-spacer'`): CSS class of the spacer span.
+- `setPreWrapStyle` (default: `true`): inject inline pre-wrap style for wrap-enabled blocks.
+- `sampLang` (default: `'shell,console'`): additional fence langs rendered as `<samp>`.
+- `langPrefix` (default: `md.options.langPrefix || 'language-'`): class prefix for language class.
+- `useHighlightPre` (default: `false`): passthrough highlighter `<pre><code>` wrappers and skip line-splitting features.
+- `onFenceDecision` (default: `null`): debug hook for per-fence branch decisions.
+- `onFenceDecisionTiming` (default: `false`): include timing fields in `onFenceDecision`.
+
+`em-lines` syntax note:
+
+- supports single values (`2`) and ranges (`4-6`)
+- supports open-ended forms (`3-`, `-2`)
+- reversed ranges are normalized (`5-3` behaves as `3-5`)
+
+Migration note (`0.5.0`):
+
+- `comment-line` / `data-pre-comment-line` / `pre-comment-line` were removed
+- use `comment-mark` / `data-pre-comment-mark` / `pre-line-comment`
+
+## Custom Highlight API Mode (Experimental / Advanced)
+
+Custom Highlight API mode renders plain code text and emits range payloads for browser-side Custom Highlight API application.
+
+Important:
+
+- You must run runtime apply in the browser (`applyCustomHighlights` or `observeCustomHighlights`).
+- Without runtime apply, payload exists but browser highlights are not activated.
+- `test/custom-highlight/pre-highlight.js` is a demo helper, not the package runtime API contract.
+
+Use API mode only if you need runtime range highlighting and can manage runtime/CSS integration in your app.
+
+### Minimal API Example (Shiki provider)
+
+```js
+import MarkdownIt from 'markdown-it'
+import markdownItAttrs from 'markdown-it-attrs'
+import { createHighlighter } from 'shiki'
+import rendererFenceApi, {
+  applyCustomHighlights,
+  renderCustomHighlightPayloadScript,
+} from '@peaceroad/markdown-it-renderer-fence/custom-highlight'
+// Dispatcher entry alternative:
+// import rendererFenceApi from '@peaceroad/markdown-it-renderer-fence'
+
+const highlighter = await createHighlighter({
+  themes: ['github-light'],
+  langs: ['javascript', 'typescript', 'json'], // preload grammars; Shiki does not auto-detect language
+})
+
+const md = MarkdownIt({ html: true })
+  .use(markdownItAttrs)
+  .use(rendererFenceApi, {
+    // highlightRenderer: 'api', // required only with dispatcher entry
+    customHighlight: {
+      provider: 'shiki',
+      highlighter,
+      theme: 'github-light',
+      transport: 'env',
+    },
+  })
+
+const env = {}
+const html = md.render('```js\nconst x = 1\n```', env)
+const payloadScript = renderCustomHighlightPayloadScript(env) // id="pre-highlight-data"
+```
 
-The following options can be specified when initializing the plugin:
+Browser-side apply:
 
-- attrsOrder: default ['class','id','data-*','style'] — order of attributes in output; wildcards supported.
-- setHighlight: default true — enable calling highlight function (e.g., highlight.js).
-- setLineNumber: default true — wrap lines in spans for line numbers.
-- setEmphasizeLines: default true — enable emphasis based on emphasize-lines attribute.
-- lineEndSpanThreshold: default 0 — character count threshold to append end-of-line span (0 to disable).
-- setLineEndSpan: alias for lineEndSpanThreshold.
-- lineEndSpanClass: default 'pre-lineend-spacer' — CSS class for end-of-line span.
-- setPreWrapStyle: default true — include inline pre-wrap styles on `<pre>` when wrap is enabled.
-- sampLang: default 'shell,console' — comma-separated list of languages (in addition to 'samp') that will be rendered using `<samp>`.
-- langPrefix: default md.options.langPrefix || 'language-' — prefix for language class on code blocks.
-- useHighlightPre: default false — if highlight returns `<pre><code>`, keep that wrapper and skip line-splitting features; attributes are still merged.
+```js
+applyCustomHighlights(document)
+```
+
+When using `colorScheme: 'auto'`, scheme resolution happens at apply time.
+If OS/browser theme changes after first apply, re-run apply (or use observer watch mode below).
+
+If you only need runtime apply on the browser, import runtime-only entry:
+
+```js
+import { observeCustomHighlights } from '@peaceroad/markdown-it-renderer-fence/custom-highlight-runtime'
+```
+
+`langs` note:
+
+- `createHighlighter({ langs: [...] })` should include the languages you expect to render.
+- Shiki does not auto-detect language from code text.
+- if a target language is not loaded, this plugin falls back to Shiki `text` tokenization for that block (safe, but no syntax color buckets).
+
+### Minimal API Example (highlight.js provider)
+
+```js
+import MarkdownIt from 'markdown-it'
+import markdownItAttrs from 'markdown-it-attrs'
+import hljs from 'highlight.js'
+import rendererFenceApi from '@peaceroad/markdown-it-renderer-fence/custom-highlight'
+// Dispatcher entry alternative:
+// import rendererFenceApi from '@peaceroad/markdown-it-renderer-fence'
+
+const md = MarkdownIt({ html: true })
+  .use(markdownItAttrs)
+  .use(rendererFenceApi, {
+    // highlightRenderer: 'api', // required only with dispatcher entry
+    customHighlight: {
+      provider: 'hljs',
+      hljsHighlight: (code, lang) => {
+        if (lang && hljs.getLanguage(lang)) {
+          return hljs.highlight(code, { language: lang }).value
+        }
+        return hljs.highlight(code, { language: 'plaintext' }).value
+      },
+      transport: 'env',
+    },
+  })
+```
+
+### API Providers
+
+- `customHighlight.provider: 'shiki'`  
+  Requires `customHighlight.highlighter.codeToTokens(...)` (synchronous).
+- `customHighlight.provider: 'hljs'`  
+  Uses `customHighlight.hljsHighlight`, fallback to `customHighlight.highlight`, then `md.options.highlight`.
+- `customHighlight.provider: 'custom'`  
+  Escape hatch. Requires synchronous `customHighlight.getRanges(...)`.
+
+### Shiki Scope Modes
+
+- `auto` (default)
+- `color`
+- `semantic`
+- `keyword` (best for stable CSS-managed styling)
+
+Migration note (`0.5.0`):
+
+- legacy aliases like `json`, `bucket`, `keyword-only` are removed
+- use canonical values: `auto | color | semantic | keyword`
+
+Recommended production profile for API mode:
+
+```js
+customHighlight: {
+  provider: 'shiki',
+  shikiScopeMode: 'keyword',
+  includeScopeStyles: false
+}
+```
+
+### API Multi-Theme (Shiki, `v:1` additive payload)
+
+When you need runtime light/dark switching with Shiki color styles, pass object form theme:
+
+```js
+customHighlight: {
+  provider: 'shiki',
+  highlighter,
+  shikiScopeMode: 'color',
+  includeScopeStyles: true,
+  theme: {
+    light: 'github-light',
+    dark: 'github-dark',
+    default: 'light',
+  },
+}
+```
+
+Runtime apply can choose variant:
+
+```js
+applyCustomHighlights(document, { colorScheme: 'auto' }) // 'auto' | 'light' | 'dark'
+```
+
+Auto re-apply on color-scheme change:
+
+```js
+observeCustomHighlights(document, {
+  applyOptions: { colorScheme: 'auto', incremental: true },
+  watchColorScheme: true,
+})
+```
+
+### CMS / Copy-Paste Operation
+
+If you copy rendered HTML+payload JSON into another CMS/page:
+
+- API mode works only when runtime JS is also available on that page.
+- payload JSON alone is not enough.
+- if the target CMS cannot run custom JS, use `markup` mode instead.
+- this plugin does not auto-generate/write runtime JS files during markdown render.
+
+Practical patterns:
+
+1. Site/app with bundler  
+   Bundle `@peaceroad/markdown-it-renderer-fence/custom-highlight-runtime` and run `observeCustomHighlights(...)`.
+2. Static page with module scripts  
+   Load runtime entry via your ESM delivery path and call `applyCustomHighlights(...)`.
+3. HTML-only CMS (no JS injection)  
+   Use `markup` mode (API mode is not suitable).
+
+### CLI Build Artifact Contract
+
+For CLI/static generation, treat API mode output as two artifacts:
+
+1. HTML artifact  
+   Includes `<pre data-pre-highlight="...">...</pre>` and payload JSON (`env` script or inline-script transport).
+2. Runtime artifact  
+   Browser JS that imports `@peaceroad/markdown-it-renderer-fence/custom-highlight-runtime` and runs `applyCustomHighlights(...)` or `observeCustomHighlights(...)`.
+
+Typical runtime bridge file:
+
+```js
+import { observeCustomHighlights } from '@peaceroad/markdown-it-renderer-fence/custom-highlight-runtime'
+
+observeCustomHighlights(document, {
+  applyOptions: { colorScheme: 'auto', incremental: true },
+  watchColorScheme: true,
+})
+```
+
+Then include that bridge in generated HTML:
+
+```html
+<script type="module" src="/assets/custom-highlight-runtime.js"></script>
+```
 
-When `useHighlightPre` is true and the highlight output contains `<pre><code>`, line-splitting features are disabled (setLineNumber, setEmphasizeLines, lineEndSpanThreshold, comment-line). In this mode `<samp>` conversion is not possible, so avoid `useHighlightPre` when you need samp output.
+### API Options
+
+- `highlightRenderer` (`'markup' | 'api' | 'custom-highlight-api'`, default: `'markup'`): dispatcher mode selector (`/custom-highlight` entry does not need this).
+- `customHighlight.provider` (default: `'shiki'`): range source (`'shiki' | 'hljs' | 'custom'`).
+- `customHighlight.getRanges`: required when `provider: 'custom'`; must return synchronous ranges.
+- `customHighlight.highlighter`: Shiki highlighter object with synchronous `codeToTokens`.
+- `customHighlight.hljsHighlight`: highlight.js-style function used when `provider: 'hljs'`.
+- `customHighlight.highlight`: fallback highlight function for `hljs` provider.
+- `customHighlight.defaultLang`: default language when fence language is empty.
+- `customHighlight.theme`: Shiki theme name string, or object `{ light, dark, default? }` for dual-theme payload.
+- `customHighlight.shikiScopeMode` (default: `'auto'`): scope naming mode (`auto | color | semantic | keyword`).
+- `customHighlight.shikiKeywordClassifier`: custom classifier hook for keyword mode.
+- `customHighlight.shikiKeywordLangResolver`: custom language resolver hook for keyword mode.
+- `customHighlight.shikiKeywordLangAliases`: language alias map for keyword resolver.
+- `customHighlight.includeScopeStyles` (default: `true`): include payload `scopeStyles` when available.
+- `customHighlight.fallback` (`'plain' | 'markup'`, default: `'plain'`): server-side fallback renderer on provider errors.
+- `customHighlight.fallbackOn`: restrict fallback trigger reasons.
+- `customHighlight.transport` (`'env' | 'inline-script'`, default: `'env'`): payload transport target.
+- `customHighlight.idPrefix` (default: `'hl-'`): generated per-block payload id prefix.
+- `customHighlight.scopePrefix` (default: `'hl'`): scope name prefix used for highlight registration.
+- `customHighlight.lineFeatureStrategy` (`'hybrid' | 'disable'`, default: `'hybrid'`): keep or disable line-span features in API rendering.
+
+### API Helper Exports
+
+- `applyCustomHighlights`
+- `observeCustomHighlights`
+- `clearCustomHighlights`
+- `shouldRuntimeFallback`
+- `getCustomHighlightPayloadMap`
+- `renderCustomHighlightPayloadScript`
+- `renderCustomHighlightScopeStyleTag`
+- `customHighlightPayloadSchemaVersion`
+- `customHighlightPayloadSupportedVersions`
+
+## Docs and Examples
+
+- API styling guide: `docs/custom-highlight-styling-guide.md`
+- default preset CSS sample: `docs/default-highlight-theme.css`
+- provider matrix page: `example/custom-highlight-provider-matrix.html`
+
+## Tests and Benchmarks
+
+- all tests: `npm test`
+- provider contract: `npm run test:provider:contract`
+- keyword coverage: `npm run test:provider:keyword`
+- keyword holdout parity: `npm run test:provider:keyword:holdout`
+- performance baseline: `npm run test:performance`
+- runtime apply benchmark: `npm run test:performance:runtime`
+
+## License and Notices
+
+- Project license: MIT (`LICENSE`)
+- Third-party notices: `THIRD_PARTY_NOTICES.md`
+- `docs/default-highlight-theme.css` contains mappings derived from highlight.js theme families (BSD-3-Clause; see notices).

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,56 @@
+# Third-Party Notices
+
+This repository is licensed under MIT (see `LICENSE`), and also contains documentation assets derived from third-party themes.
+
+## highlight.js theme references used in docs
+
+Files:
+
+- `docs/default-highlight-theme.css`
+
+Source references:
+
+- `highlight.js` style family (GitHub / GitHub Dark)
+- Upstream paths (for reference):
+  - `node_modules/highlight.js/styles/github.css`
+  - `node_modules/highlight.js/styles/github-dark.css`
+
+Upstream license:
+
+- BSD 3-Clause License
+- Copyright (c) 2006, Ivan Sagalaev.
+
+Full upstream license text:
+
+```text
+BSD 3-Clause License
+
+Copyright (c) 2006, Ivan Sagalaev.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+```
+