refactor(worker): use initSync for direct module init

[magic-akari]

Summary

Since the WebAssembly.Module is already available when the worker receives the message (passed via event.data), we can directly use initSync for synchronous initialization instead of async initWasm.

This eliminates unnecessary async overhead and simplifies the code by removing the async branch that was designed for lazy module loading.

Test Plan

Tested locally by running the demo project. Awaiting GitHub CI test results for further validation.

[gemini-code-assist]

Summary of Changes

Hello @magic-akari, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the WebAssembly module initialization process within the worker. By leveraging the fact that the WebAssembly.Module is already available when the worker receives its initial message, the code now uses a synchronous initialization method, initSync, instead of the previously asynchronous initWasm. This change streamlines the worker setup, reducing complexity and potential performance overhead associated with asynchronous operations in this specific context.

Highlights

• WebAssembly Initialization Refactor: Switched from asynchronous initWasm to synchronous initSync for WebAssembly module initialization within the worker, leveraging the fact that the module is already available.
• Performance and Code Simplification: Eliminated unnecessary async overhead and simplified the worker's initialization logic by removing the async branch previously designed for lazy module loading.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the worker initialization to use initSync instead of the asynchronous initWasm. This is a good simplification, as the WebAssembly module is already available, making the synchronous initialization path more efficient and the code easier to follow. The changes are correct and well-motivated. I have one suggestion to improve error logging.

[Copilot]

Pull request overview

This PR refactors the loader worker initialization to use synchronous WASM initialization instead of asynchronous, eliminating unnecessary async overhead. Since the WebAssembly.Module and WebAssembly.Memory are already available when the worker receives the message (passed via postMessage from the main thread), there's no need for async initialization.

Changes:

• Replaced async initWasm with synchronous initSync for direct module initialization
• Changed the onmessage handler from async to synchronous
• Updated error handling from promise-based .catch() to try-catch block

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.