Bump devDependencies and update lockfile

[coliff]

Upgrade several devDependencies and regenerate package-lock.json. Notable bumps: @eslint/js 10.0.0→10.0.1, @rollup/plugin-commonjs 28.0.6→29.0.2, @rollup/plugin-terser ^0.4.4→^1.0.0, @types/node ^20.19.0→^20.19.37. Lockfile reflects updated transitive deps (serialize-javascript → 7.0.4, flatted → 3.4.2), updated resolved/integrity fields, and removal of legacy randombytes/safe-buffer entries. Terser/serialize-javascript now declare Node >=20.0.0. No application code changes.

[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 focuses on maintaining the project's development environment by updating various development dependencies and regenerating the package-lock.json file. The updates ensure compatibility with newer Node.js versions and remove outdated transitive dependencies, contributing to a more robust and current build process without altering any application code.

Highlights

• Development Dependency Updates: Several key development dependencies have been updated, including @eslint/js from 10.0.0 to 10.0.1, @rollup/plugin-commonjs from 28.0.6 to 29.0.2, @rollup/plugin-terser from ^0.4.4 to ^1.0.0, and @types/node from ^20.19.0 to ^20.19.37.
• Transitive Dependency Bumps: Transitive dependencies serialize-javascript was updated from 6.0.2 to 7.0.4 and flatted from 3.3.3 to 3.4.2, reflecting updates in the dependency tree.
• Node.js Version Requirement: The minimum Node.js version requirement for @rollup/plugin-terser and serialize-javascript has been raised to >=20.0.0.
• Lockfile Cleanup: Legacy entries for randombytes and safe-buffer have been removed from package-lock.json, streamlining the dependency graph.

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

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 several development dependencies, including major version bumps for @rollup/plugin-commonjs and @rollup/plugin-terser. The changes are consistent with the project's Node.js v20 requirement, and the lockfile is correctly updated. I've added a comment regarding the dependency versioning strategy to improve consistency and maintainability.

[Copilot]

Pull request overview

This pull request updates root-level devDependencies and regenerates package-lock.json to reflect updated direct and transitive tooling packages used for linting and builds.

Changes:

• Bump devDependencies: @eslint/js, @rollup/plugin-commonjs, @rollup/plugin-terser, and @types/node.
• Regenerate package-lock.json to align resolved versions/integrity fields and updated transitive dependencies (e.g., serialize-javascript, flatted), and remove no-longer-needed legacy entries.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates devDependency versions for ESLint/Rollup tooling and Node typings.
package-lock.json	Regenerates lockfile to match bumped devDependencies and updated transitive dependency graph/metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.