v5.0.5

Local images now resolve from every prose source, plus JSDoc staticFiles support and a generated sitemap.xml. Parity across the JSDoc and TypeDoc bridges.

Images

• Local images referenced from tutorials, the README, and JSDoc / TypeScript doc comments (previously only opts.docs) are copied into the content-hashed _assets/ pipeline and the reference is rewritten — both Markdown ![](…) and raw <img>. Comment images resolve against each symbol's own source file; SVGs are inlined so light/dark follows the theme toggle.
• JSDoc templates.default.staticFiles is honored: included files are copied verbatim to the output root, and the include directories become fallback search roots, so a bare reference like ![](classes-io.png) resolves and is hashed — no need to rewrite existing comments or tutorials. A file already served from _assets/ is not duplicated at the root.
• Image syntax shown inside code spans / fenced blocks is left literal — no spurious copy, rewrite, or "could not read image" warning.

Sitemap

• New siteUrl option: when set, the build emits sitemap.xml at the output root with one <loc> per non-hidden page. Only the URL's origin is used; the deploy sub-path comes from basePath, so the two never double-count.

Security

• No runtime security-surface changes. Image and staticFiles resolution runs at build time over author-declared paths only — no runtime evaluation and no new network access; siteUrl is used solely to compose the absolute <loc> URLs in sitemap.xml.

Full changelog: v5.0.4...v5.0.5