docs(web_generator): document minimum supported Node.js version

[harrshita123]

This PR documents the minimum supported Node.js version for web_generator.

Recent discussions highlighted that behavior can differ across Node versions, especially when running the generator under Node’s ESM environment. To avoid confusion and reduce the risk of similar issues in the future, this change clarifies that web_generator requires Node.js v22 or newer.

This aligns with the Node versions currently used in CI and with prior discussions (for example, #427), where differences in behavior across Node versions were observed.

Why this change

The generator relies on Node features and behavior that are only consistent in newer Node versions. Clearly documenting the minimum supported version helps set the right expectations for contributors and users, and avoids the need for extra compatibility work or additional CI coverage for older Node releases.

Scope

This is a documentation-only change. No generator logic or runtime behavior is modified.

[gemini-code-assist]

Summary of Changes

Hello @harrshita123, 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 formally documents the minimum required Node.js version (v22 or newer) for the web_generator. This update aims to provide clear guidance to users and contributors, ensuring consistent tool behavior and preventing compatibility issues that can arise from using older Node.js environments, especially within its ESM context.

Highlights

• Minimum Node.js Version Documented: The web_generator now explicitly states that Node.js v22 or newer is required for its operation.
• Compatibility Clarification: This documentation update aims to prevent runtime failures and inconsistent behavior, particularly in Node's ESM environment, which can occur with older Node.js versions.
• Documentation-Only Change: This pull request solely focuses on updating documentation; no changes have been made to the generator's logic or runtime behavior.

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 adds documentation for the minimum required Node.js version (v22 or newer) for web_generator. This is a helpful clarification for contributors and users, preventing potential issues with unsupported Node.js versions. The change is clear and well-justified. I have one minor suggestion to improve formatting in the README file.

[gemini-code-assist]

For better readability and consistency, this extra blank line can be removed. A single blank line is sufficient to separate sections in Markdown files.

[srujzs]

FYI @nikeokoronkwo