Execute implementation plan for WASM binary optimization#16
Execute implementation plan for WASM binary optimization#16
Conversation
This commit implements the optimization stages described in docs/PLAN.md: - Eliminated `crypto/md5` from WASM builds by stubbing out attachments. - Unified font and image ID generation, removing `crypto/sha1` dependency. - Unified JSON decoding using `tinywasm/json`. - Unified time handling to use `int64` (Unix nanoseconds) throughout the library. - Removed direct `os` package dependencies from shared files, using injected `readFile` instead. - Added appropriate build tags to isolate backend-only logic. - Updated tests and examples to reflect the API changes. Final WASM binary size was reduced from 3.9M to 3.7M. All tests pass on the backend. Co-authored-by: cdvelop <44058491+cdvelop@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
I have completed the implementation of the WASM optimization plan. Key changes include:
crypto/md5andcrypto/sha1from the WASM binary.ospackage usage in shared files.int64for dates and makingSVGBasicFileParsea method ofFpdf.PR created automatically by Jules for task 16760240081700674875 started by @cdvelop