refactor(wasm): simplify build logic and optimize initialization

[xusd320]

This PR follows up on the HMR work, focusing on code simplification in crates/utoo-wasm/src/pack.rs.

Changes:

• Removed the PackProject struct implementation block (impl PackProject).
• Moved the build logic directly into the exported build function.
• Optimized init_pack_project to avoid redundant re-initializations when the mode (dev/prod) hasn't changed.
• Removed the wrapper run_pack function.

[gemini-code-assist]

Summary of Changes

Hello @xusd320, 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 focuses on refactoring the WebAssembly (WASM) build process to enhance code clarity and operational efficiency. It simplifies the core build logic by removing an unnecessary struct implementation and integrating its functionality directly into the main build function. Additionally, it introduces an optimization to prevent redundant project initializations, contributing to a more streamlined and performant build pipeline.

Highlights

• Code Simplification: The PackProject struct's implementation block has been removed, streamlining the code structure.
• Build Logic Relocation: The core build logic, previously a method of PackProject, has been moved directly into the exported build function for better accessibility and reduced indirection.
• Initialization Optimization: The init_pack_project function has been optimized to prevent redundant re-initializations when the development/production mode remains unchanged, improving efficiency.
• Wrapper Function Removal: The run_pack wrapper function has been removed, further simplifying the build process.

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 build logic in crates/utoo-wasm/src/pack.rs by removing the PackProject::build method and inlining its logic directly into the build function. This simplifies the code by removing a layer of indirection. The changes also include updates to the auto-generated TypeScript definitions in index.d.ts.

While reviewing, I found an issue in the logging code that was moved. The logic to get the number of applications and libraries for the trace message seems to be incorrect as it tries to access fields on a ResolvedVc without awaiting it first, which will likely lead to a compilation error. I've provided a suggestion to fix this.