doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

The tree ships the sheet generator and its places file, not just the pool

Browse source 
generate-tree gathers assets in two stages: a pool, then an allowlist of
what the tree serves. ne-places.json and lib/poster-render.js were added to
the pool only, so every `bun run tree` deleted the served copies the two
commits before this one checked in, and a print would 404 the generator.
Both are now in the allowlist; a regenerated tree keeps them byte-identical
to their sources, and check:poster-render-pinned passes on it.
This commit is contained in:
Doxa Maps 2026-09-29 06:25:43 +00:00
parent 0be5f07ab6
commit 399aa20bfa
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
internal/generate-tree.mjs
View file

@ -1771,6 +1771,11 @@ function main() {
'boundaries/world-adm0-web.geojson', // the web copies the interactive maps fetch
'boundaries/gb-IND-ADM1-web.geojson',
'boundaries/gb-IND-ADM1-full-web.geojson',
// The map-sheet generator's two print-time fetches (library/packet/posterSheets.js): the capitals and
// cities it draws, and the generator itself (sha384-pinned in poster-render.integrity.js). Both were
// gathered into the pool above but, missing here, never reached the tree: a print would 404.
'boundaries/ne-places.json',
'lib/poster-render.js',
// people-groups — all-people-groups.vue (the slim JSON only; NOT the 16 MB CSV,
// which no element fetches and which dropin.exclude already withholds).
'people-groups/people-groups-slim.json',