Update packages

[Lokowitz]

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

How to test?

[gemini-code-assist]

Summary of Changes

Hello @Lokowitz, 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 a comprehensive update of the project's development environment and dependencies. It involves advancing the Node.js runtime to version 24, ensuring compatibility with the latest build tools, and updating a wide array of third-party packages to their most recent stable releases. Additionally, the TypeScript compilation target has been bumped to ES2024, aligning the project with newer JavaScript language features.

Highlights

• Node.js Version Upgrade: The base Node.js version in the development Dockerfile has been upgraded from Node.js 22 to Node.js 24, along with updating the esbuild target to Node.js 24.
• Development Environment Dependencies: The Dockerfile now includes python3, make, and g++ to support the compilation of native Node.js modules.
• Package Dependency Updates: Numerous dependencies in package.json have been updated to their latest minor or patch versions, covering various libraries including AWS SDK, React Email components, Tanstack Query, Next.js, React, and Stripe.
• TypeScript Target Update: The TypeScript compilation target across all tsconfig files (tsconfig.enterprise.json, tsconfig.oss.json, tsconfig.saas.json) has been updated from ES2022 to ES2024.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 updates various dependencies in the package.json file, upgrades the Node.js version in the Dockerfile.dev and esbuild.mjs files, and updates the target ECMAScript version in the tsconfig.json files. The dependency updates appear routine, but the Node.js and ECMAScript version upgrades should be reviewed for compatibility and potential impact on the codebase.

[gemini-code-assist]

high: Upgrading the base image node version can introduce breaking changes. Ensure that all dependencies and the application code are compatible with Node.js 24.

[gemini-code-assist]

high: Ensure that the target node24 is compatible with the project's dependencies and runtime environment. Verify that all features used are supported in Node.js 24.

[gemini-code-assist]

high: Ensure that the target ES2024 is compatible with the project's dependencies and runtime environment. Verify that all features used are supported in ES2024.

[gemini-code-assist]

high: Ensure that the target ES2024 is compatible with the project's dependencies and runtime environment. Verify that all features used are supported in ES2024.

[gemini-code-assist]

high: Ensure that the target ES2024 is compatible with the project's dependencies and runtime environment. Verify that all features used are supported in ES2024.

[gemini-code-assist]

medium: Consider using environment variables for sensitive information instead of hardcoding them directly in the code. This is a general security best practice.