mokhtar/nxdns
1
0
Fork 0
Code Pull Requests Actions Packages Releases 13 Activity

rename web/ to admin/, along with the web-named build and cli identifiers

Browse Source
This commit is contained in:
mokhtar
2026-08-16 00:17:58 +02:00
parent 5b3d1cd65c
commit 1e97c80f6b
136 changed files with 196 additions and 196 deletions
Download Patch File Download Diff File Expand all files Collapse all files
licenses/dependency-identity.txt
+6 -6
View File
@@ -1,6 +1,6 @@
The identity of the dependency sets that decide what licenses/inventory.zon has
to cover. This file is a snapshot, not a source: src/licenses_drift_test.zig
recomputes each section from build.zig.zon and web/package-lock.json and fails
recomputes each section from build.zig.zon and admin/package-lock.json and fails
when it disagrees with what is recorded here. Prose before the first section
header is ignored by the guard.
@@ -10,11 +10,11 @@ shipped bytes first, then record it.
The runtime closure is every lockfile package not marked `dev`. That is a
superset of what the bundler emits — the guard cannot run rollup — so packages
tree-shaken out of web/dist appear here too; the inventory explains each of them
tree-shaken out of admin/dist appear here too; the inventory explains each of them
instead of carrying its licence.
The bundled-packages section is the one the Zig guard cannot compute: it is the
set of npm packages that actually contribute a module to web/dist, read off the
set of npm packages that actually contribute a module to admin/dist, read off the
sourcemap `sources` lists of a `vite build --sourcemap`. Only the frontend gate
can produce it, so gates.yml recomputes it there and fails on a difference. It
is what closes the hole the runtime-closure section leaves open — a package
@@ -28,9 +28,9 @@ digest both change the line, which forces somebody to re-read what the new base
ships before the inventory can claim it.
The generators section is the other direction: packages the lockfile marks `dev`
whose own output nevertheless ends up in web/dist, and so in the binary. Its
whose own output nevertheless ends up in admin/dist, and so in the binary. Its
membership is a judgement, not a query — it was settled by reading a
`vite build --sourcemap` of web/, both the sourcemap `sources` lists and the
`vite build --sourcemap` of admin/, both the sourcemap `sources` lists and the
regions of each chunk no sourcemap segment maps back to a source file. The
versions here are read from the lockfile like any other section.
@@ -80,7 +80,7 @@ vite 8.1.5 MIT
[container base image]
alpine:3.22@sha256:14358309a308569c32bdc37e2e0e9694be33a9d99e68afb0f5ff33cc1f695dce
[npm packages bundled into web/dist]
[npm packages bundled into admin/dist]
@internationalized/string
@stylexjs/stylex
@tanstack/history