chore: moving core dev dependencies to mono hoist

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
chore: moving core dev dependencies to mono hoist

[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 refactors the project's development dependency management by centralizing common dev dependencies in the root package.json. This strategic move utilizes monorepo hoisting to eliminate redundant package installations across various sub-packages, leading to a cleaner, more efficient, and easier-to-maintain dependency structure. The changes are reflected across multiple package.json files and the pnpm-lock.yaml to ensure consistency and proper resolution.

Highlights

• Centralized Dev Dependencies: Moved common development dependencies, specifically @faker-js/faker, @types/node, and rimraf, from individual package devDependencies to the root package.json.
• Monorepo Hoisting: Leveraged pnpm's hoisting capabilities to reduce dependency duplication and streamline package installations across the monorepo.
• Lockfile Optimization: Updated the pnpm-lock.yaml to reflect the hoisted dependencies and removed obsolete entries, ensuring a consistent and optimized dependency graph.

Changelog

• package.json
  • Added @faker-js/faker, @types/node, and rimraf to the root devDependencies.
• packages/cache-manager/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/cacheable-request/package.json
  • Removed @types/node and rimraf from devDependencies.
• packages/cacheable/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/file-entry-cache/package.json
  • Removed @types/node and rimraf from devDependencies.
• packages/flat-cache/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/memory/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/net/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/node-cache/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/utils/package.json
  • Removed @faker-js/faker, @types/node, and rimraf from devDependencies.
• packages/website/package.json
  • Removed @types/node and rimraf from devDependencies.
• pnpm-lock.yaml
  • Added @faker-js/faker, @types/node, and rimraf to the root devDependencies.
  • Removed these dependencies from individual package devDependencies.
  • Cleaned up various older and unused dependency entries from the lockfile.
  • Updated @types/node versions in dependent packages to align with the hoisted version.

Activity

• Author confirmed adherence to contributing guidelines and code of conduct.
• Author confirmed tests for changes have been added with 100% code coverage.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c711fb7) to head (aae3c85).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1596   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2473      2473           
  Branches       559       558    -1     
=========================================
  Hits          2473      2473           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request correctly moves common development dependencies to the root package.json for hoisting, which is a good practice for monorepo maintainability. However, there is a critical issue with the version specified for @types/node. The version ^25.3.0 is invalid and will cause dependency installation to fail. This needs to be corrected to a valid version.