Rename /frontend/wasm -> /frontend/wrapper

[Keavon]

Part of #3664

[gemini-code-assist]

Summary of Changes

Hello, 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 renaming the /frontend/wasm directory to /frontend/wrapper to better reflect its purpose as a wrapper around the editor backend. The changes involve updating various files to reflect this renaming, ensuring that the application correctly references the new directory and its contents. This improves clarity and maintainability of the codebase.

Highlights

• Renaming: The primary focus of this pull request is to rename the /frontend/wasm directory to /frontend/wrapper, reflecting its role as a wrapper around the editor backend.
• Code Updates: The code has been updated to reflect the directory renaming, ensuring that all imports and references point to the new /frontend/wrapper location.
• Configuration Changes: Configuration files such as Cargo.toml, .nix/pkgs/graphite.nix, frontend/package.json, and frontend/eslint.config.js have been modified to align with the new directory structure.

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.

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. ↩

[cubic-dev-ai]

No issues found across 83 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

[gemini-code-assist]

Code Review

This pull request is a large-scale refactoring that renames the /frontend/wasm directory to /frontend/wrapper. This change is reflected across the entire codebase, including build scripts, configuration files, import paths in source code, and documentation. The package name has also been updated from graphite-wasm to graphite-wasm-wrapper.

The changes appear to be thorough and consistent. I have one minor suggestion to improve the clarity of the documentation in frontend/src/README.md regarding the initialization process of the WebAssembly module and the editor wrapper.

Overall, this is a solid refactoring that improves the naming and structure of the frontend components.