chore: Migrating the package manager from yarn to pnpm

[KubrickCode]

• Migrating the project-wide package manager from yarn to pnpm improved disk space efficiency and installation speed.
• While still a monorepo structure, the coupling was reduced to facilitate future repositories separation, allowing each repo to be managed as a separate workspace.

[gemini-code-assist]

Summary of Changes

Hello @KubrickCode, 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 transitions the project's package management from Yarn to pnpm. This strategic move is intended to enhance development efficiency by optimizing disk space usage and accelerating package installations. Furthermore, it includes structural adjustments to the monorepo, laying the groundwork for easier future separation of repositories into distinct workspaces.

Highlights

• Package Manager Migration: The project's package manager has been migrated from Yarn to pnpm, aiming to improve disk space efficiency and installation speed.
• Monorepo Structure Refinement: The monorepo structure has been adjusted to reduce coupling, preparing the project for potential future separation into individual repositories, each managed as a separate workspace.
• Build and Dev Scripts Updated: All yarn commands within the justfile for dependency installation, linting, building, packaging, publishing, and testing have been updated to use pnpm.
• Dev Container Configuration: The development container's node installation script has been updated to enable Corepack and activate pnpm version 9.15.0, ensuring pnpm is the default package manager in the dev environment.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/lint.yml
  • .github/workflows/release.yml
  • .github/workflows/test.yml

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

[KubrickCode]

/gemini review

[gemini-code-assist]

Code Review

This pull request successfully migrates the project's package manager from Yarn to pnpm. The changes across the configuration files and build scripts are correct and reflect the switch to pnpm. I have provided one suggestion on the justfile to leverage pnpm's workspace capabilities. Adopting this would simplify your build process and align better with both pnpm's best practices for monorepos and your repository's style guide regarding code modularization.