Why
Landing a change ended with a burst of confetti drawn from a vendored copy of
canvas-confetti. The celebration was the only consumer of that library, its
license file, and the ?merged=1 flag the landing redirect carried so a reload
would not replay it. The request page already shows the result: the change is
merged, with the commit it landed as.
Removing it drops roughly 900 lines of vendored JavaScript and one more asset to keep licensed and patched.
What changed
- Delete
server/web/static/confetti.browser.jsandserver/web/static/canvas-confetti.LICENSE. - Remove the loader and burst from
app.js, and the test that guarded it. - Remove the library from
NOTICEand the static-asset comments. - Stop adding
?merged=1after a landing. The redirect now goes to the plain request page.
The separate ?merging=1 flag for merge-when-ready is unchanged.
Verification
go test -tags sqlite_fts5 ./server -run 'TestLandingRedirectsToTheRequestPage|TestStatic'python3asset check againstNOTICEreports no findings./vole workflow check