npm update --strict-peer-deps fails

[athomas-octoberthree]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Cannot update with npm update when using the --strict-peer-deps flag.

Reproduction Link

n/a

Steps to Reproduce

1. npm init gatsby
2. npm update --strict-peer-deps

Expected Result

Updating should happen with no peer dependency conflicts, forming a good foundation for future updates, adding plugins, and adding packages.

Actual Result

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error @typescript-eslint/eslint-plugin@"^5.60.1" from [email protected]
npm error node_modules/gatsby
npm error gatsby@"^5.13.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @typescript-eslint/eslint-plugin@"^4.0.0" from [email protected]
npm error node_modules/eslint-config-react-app
npm error eslint-config-react-app@"^6.0.0" from [email protected]
npm error node_modules/gatsby

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7...
  Binaries:
    Node: 20.14.0 - ...
    Yarn: 1.22.22 - ...
    npm: 10.7.0 - ...
  Browsers:
    Edge: Chromium (123.0....)
  npmPackages:
    gatsby: ^5.13.5 => 5.13.5

Config Flags

no flags