chore(deps): 14 potentially outdated deps. High-confidence safe upgrades: jest 27→29,

[isagoakira]

🔧 依赖维护更新 — facebook/create-react-app

此 PR 由 Code Legacy Reviver 自动生成🤖

📋 更新摘要

14 potentially outdated deps. High-confidence safe upgrades: jest 27→29, eslint 8.3→8.57, @testing-library/* trio, husky 4→8, prettier 2→3 (medium risk). All changes are minor/patch except major bumps for testing libs, husky, prettier, lerna, meow, lint-staged, fs-extra, execa, puppeteer. Test after upgrade.

📦 变更清单

🔴 jest: ^27.4.3 → ^29.7.0
27.x is from 2022, latest 29.x has security fixes and Node 20+ support

🔴 eslint: ^8.3.0 → ^8.57.0
Latest 8.x patch has security fixes and updated parser configs

🔴 @testing-library/jest-dom: ^5.15.1 → ^6.4.0
Major version 6 has improved matchers, minor API changes

🔴 @testing-library/react: ^12.1.2 → ^14.1.0
13→14 stable with React 18 support, cleanup improvements

🔴 @testing-library/user-event: ^13.5.0 → ^14.4.3
Better browser simulation, upstreamed from user-event-ct

🔴 husky: ^4.3.8 → ^8.0.4
4.x is from 2019, 8.x has better cross-platform hooks support

🟡 prettier: ^2.5.0 → ^3.2.0
3.x is stable with faster formatting, may need .prettierrc adjustments

🟡 web-vitals: ^2.1.2 → ^3.3.0
3.x has better attribution and performance metrics

🟡 lerna: ^4.0.0 → ^7.4.0
7.x has workspaces-native support and fixed caching

🟡 meow: ^9.0.0 → ^12.1.0
12.x has TypeScript types and improved ESM support

🟡 lint-staged: ^12.1.2 → ^15.2.0
15.x has better error handling and filter-glob support

🟡 fs-extra: ^10.0.0 → ^11.8.0
11.x drops old Node.js APIs, requires Node 12+

🟡 execa: ^5.1.1 → ^8.0.1
8.x has template literal and improved cross-platform handling

🟢 puppeteer: ^12.0.1 → ^21.6.0
Major version bump due to Chromium bundling changes, test thoroughly

⚠️ 风险等级

🟡 Medium

📝 文件变更

• package.json

---

Generated by Code Legacy Reviver

[meta-cla]

Hi @isagoakira!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!