feat(site): add bilingual binary patch toolkit#41
Merged
Conversation
JimmyDaddy
marked this pull request as ready for review
July 20, 2026 02:42
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.
Summary
/tools/and/zh-CN/tools/Why
The existing Playground demonstrates text and JSON round trips, but users also need a practical way to validate real binary patches. The new toolkit runs the package's own Web Worker and WebAssembly implementation locally, so file contents are not uploaded to a server.
Impact
Users can now generate compatible
ENDSLEY/BSDIFF43patches, restore and verify target files, inspect patch headers, and produce copyable cross-platform compatibility reports directly from the project website.Validation
yarn site:buildyarn site:testyarn lintyarn typecheckyarn test --runInBand— 8/8 passedyarn test:webgit diff --check origin/main...HEADThe local Puppeteer launcher remains blocked by the host Chrome debugging-endpoint issue; equivalent real-browser validation passed and automated browser coverage is included for CI.