Configure Vercel Node.js 22 runtime

[fouash]

Motivation

• The project requires Node.js 22 and pnpm in range >=10 <11, so Vercel functions were updated to match the repository runtime requirements.

Description

• Updated vercel.json to set the Vercel functions runtime to nodejs22.x for the API entrypoint.
• Reformatted api/index.js to match repository Prettier/formatting style.
• Added a changeset .changeset/bright-cars-allow.md documenting the deployment runtime update.

Testing

• Ran pnpm lint and it completed successfully.
• Ran pnpm lint:style and it completed successfully.
• Ran pnpm format (Prettier) and formatting checks passed.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dirxs	Error		Feb 6, 2026 4:40pm

[gemini-code-assist]

Summary of Changes

Hello @fouash, 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 primarily focuses on aligning the Vercel deployment environment with the project's updated Node.js requirements. It ensures that the Vercel functions run on Node.js 22.x, which is crucial for compatibility and leveraging the latest features. Additionally, minor formatting adjustments were made to maintain code consistency.

Highlights

• Vercel Runtime Update: The Vercel deployment runtime for the api/index.js entrypoint has been updated from nodejs18.x to nodejs22.x to align with project requirements.
• Code Formatting: The api/index.js file was reformatted to adhere to the repository's Prettier/formatting style, specifically changing double quotes to single quotes in import statements.
• Changelog Entry: A new changeset file (.changeset/bright-cars-allow.md) was added to document the update of the Vercel runtime.

Changelog

• .changeset/bright-cars-allow.md
  • Added a new changeset file to document the Vercel runtime update to Node.js 22.
• api/index.js
  • Updated import statements to use single quotes for consistency with Prettier formatting.
• vercel.json
  • Changed the runtime for api/index.js from nodejs18.x to nodejs22.x.
  • Reformatted the JSON structure for better readability.

Activity

• The author created the pull request.
• The author provided a detailed description outlining the motivation, description of changes, and testing steps.
• The author linked to a Codex Task.

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 correctly updates the Vercel runtime to Node.js 22, aligning with the project's requirements. The changes are clear and well-documented with a changeset. I have one minor suggestion for the vercel.json file to improve its long-term readability and maintainability.

[gemini-code-assist]

For improved readability and easier future modifications, it's generally better to format arrays in JSON files across multiple lines, even if they only contain a single element. This makes it simpler to add or change routes later and makes version control diffs cleaner. While this may be the result of an automatic formatter, I'd recommend keeping the multi-line structure for this routes configuration.

	"routes": [
		{ "src": "/(.*)", "dest": "/api/index.js" }
	]