chore: add engines field to package.json

[okxint]

Summary

• Adds engines field to package.json specifying node >= 20.0.0
• This enforces the minimum Node.js version requirement, preventing build issues for contributors using incompatible versions
• Aligns with the Node.js 24 used in the deploy workflow

Closes #367

[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 standardizes the required Node.js version for the project by introducing an engines field in package.json. This ensures development environments match the deployment environment, thereby preventing common compatibility issues and streamlining the contribution process.

Highlights

• Node.js Version Enforcement: The engines field has been added to package.json to specify a minimum Node.js version of >=20.0.0.
• Build Stability: This change prevents potential build issues for contributors by ensuring they use a compatible Node.js version.
• Workflow Alignment: The specified Node.js version aligns with the Node.js 24 version currently used in the deployment workflow.

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

[deepsource-io]

DeepSource Code Review

We reviewed changes in 85bdf3b...064e9df on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
JavaScript		Mar 22, 2026 2:32p.m.	Review ↗
Secrets		Mar 22, 2026 2:32p.m.	Review ↗

[gemini-code-assist]

Code Review

This pull request adds the engines field to package.json to enforce a minimum Node.js version. This is a good practice for project consistency. I've suggested also specifying the npm version in the engines field to further reduce environment-related issues for contributors.

[jbampton]

Thanks 🏂