Repository navigation
Exclude stale build output and handle malformed demo requests - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A removed TypeScript module could remain in
dist/and silently enter the next archive. Clean the generated directory before compiling, and make the package check seed an obsolete module and verify both its removal and the exact build-file inventory. A failed compilation now leaves no old or partial distribution behind.A malformed request target such as
//[also caused an unhandled URL error that terminated the local demo server. Return HTTP 400 and keep serving subsequent requests. Isolate the server factory so HTTP regression tests can use an ephemeral loopback port; run them in each core CI job.Extend the public-API tests to all 912 supported prefix/payload length combinations, including 128/129-character input boundaries. An independent exact-ratio oracle verifies 1,766 count/budget pairs around floating-point length cutoffs, including maximum safe counts, subnormal probabilities and unattainable budgets. Update the README, evidence methods and changelog with the scope and reproducible commands.
Validation on Node 24.19.0: 25 core tests, TypeScript, 2 HTTP integration tests and the offline installed-package check pass. A separate isolated fault-injection audit detected all eight manually selected defects (Unicode normalization, input length, rounding, namespace/length checks, biased sampling, repeated configuration reads and checksum constant). This is finite test evidence, not a proof of correctness. CI run 40481567516 is successful on head
af2f4d8ba747a930a970550b133e44fc32e86306: five core jobs on Node 22/24/26 across Linux, Windows and macOS, plus all nine Chromium/Firefox/WebKit tests. The first browser attempt was canceled during unusually slow Ubuntu package downloads; a retry completed successfully.The runtime code, public API, reference format and measured JavaScript bytes are unchanged. This remains the unreleased 0.1.0-alpha.1 candidate; no npm publication or GitHub Release is created.