Commit56d8831fRecorded10 Jun 2026Repositorysigil-site
Generate _pkg manifests for the browser bridge packages
Message
The bridge packages (sigil-browser, sigil-wasm-dom/net/canvas2d/gl, sigil-wasm-runtime) stage their JS assets through custom tasks:, which skips the default copy-package-docs step, so the monorepo dev build never emits a _pkg manifest for them and their package pages silently fail to render on usesigil.org even though their module .json docs generate. Add them to MONOREPO_PACKAGES so ensure_pkg_manifest fills the gap, and drop sigil-web-run, which no longer exists in the monorepo.
Changed
publish.sh | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)Diff
publish.shmodified
@@ -88,13 +88,20 @@ DOMAIN="usesigil.org"
88
# Core libraries whose API docs appear on usesigil.org 89
# --------------------------------------------------------------------------- 90
−91
# Monorepo packages (built from ../sigil)−92
# Post-pivot: codeberg:sigil/sigil hosts only sigil-cli + sigil-run + sigil-web-run.−93
# All language internals + libraries live in their own repos.+91
# Monorepo packages (built from ../sigil) that need a _pkg manifest+92
# generated when their custom tasks: skip the default copy-package-docs+93
# step. The browser/WASM bridge packages all stage JS assets through+94
# custom tasks, so without this list their package pages never render+95
# on the site even though their module .json docs generate fine. 96
MONOREPO_PACKAGES=( 97
sigil-cli 98
sigil-run−97
sigil-web-run+99
sigil-browser+100
sigil-wasm-runtime+101
sigil-wasm-dom+102
sigil-wasm-net+103
sigil-wasm-canvas2d+104
sigil-wasm-gl 105
) 106
107
# Extracted repos (cloned as peer directories and built individually).