From 17d1a07cf895ab033a2bf9441a12c96727214b67 Mon Sep 17 00:00:00 2001 From: Doxa Maps Date: Tue, 29 Sep 2026 21:14:06 +0000 Subject: [PATCH] README: the one-map recipe regenerates the tree too, so a .meta.json change reaches the pages From exp's second read of 4bcce8ff8. "BUNDLE= bun x vite build && bun run fix:sri" is right for a code change, but a change to the map's .meta.json reaches its pages and the manifest only through bun run tree. Without it the leaf page ships the old settings, and the landing scan's step 2b refuses the stale tree. The recipe is now "BUNDLE= bun x vite build && bun run tree && bun run fix:sri". The tree step takes a few seconds and changes nothing when nothing changed. --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 858d2621f..d69535604 100644 --- a/README.md +++ b/README.md @@ -76,12 +76,13 @@ bun run dev # open the address it prints: that page is the P **2. Build.** The built maps are already in the repo. After a change, rebuild just that map, or all of them: ```bash -BUNDLE= bun x vite build && bun run fix:sri # one map, then refresh its integrity hashes -BUILD_ALLOW=1 bun run build # every map (~4 min); the output is public/dx-maps/ +BUNDLE= bun x vite build && bun run tree && bun run fix:sri # one map, then its pages and hashes +BUILD_ALLOW=1 bun run build # every map (~4 min); the output is public/dx-maps/ ``` -Skip `fix:sri` after a one-map build and the map's own page and any pasted snippet refuse the new file, because -they still carry the old integrity hash. When the DX Life site's repo sits next to this one (`../doxa-life`), the full build also copies the maps into +After a one-map build, `bun run tree` rewrites the map's pages and the manifest (a changed `.meta.json` reaches +them only this way), and `fix:sri` refreshes their integrity hashes. Skip them and the map's own page and any pasted +snippet keep the old settings and refuse the new file. When the DX Life site's repo sits next to this one (`../doxa-life`), the full build also copies the maps into its `public/`. That is the one path set in `vite.doxa-maps-build-config.json` (`dropin.dest`); nothing else on your computer is searched. No site there: the step says so and skips. `DOXA_DROPIN=off` turns it off, and `bun run dropin` copies on demand.