Losing compatibility with node <20

[eparisio]

Describe the bug

Hi, i'm here to report a recently update compatibility issue in the package imports, that breaks the compatibility with node under v20.
15 days ago the package @microsoft/api-extractor had update a minor version v7.52.10, where they update the minimatch package to v10.0.3, who remove the compatibility with node under v20.
https://github.com/microsoft/rushstack/blob/main/apps/api-extractor/CHANGELOG.md#75210
In your package there is the import of: "@microsoft/api-extractor": "^7.50.1"

that will import the most recent minor and patch version.
the last version of @microsoft/api-extractor that will not break the compatibility should be the v7.52.9

this update is breaking our production build

package.json

Reproduction

https://codesandbox.io/p/sandbox/react-test-environment-forked-8y936d

Steps to reproduce

run npm install,
errors will appears with warnings of unsupported versions for minimatch@10.0.3 and his dependences

System Info

System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M2 Pro
    Memory: 106.34 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm
  Browsers:
    Chrome: 139.0.7258.155
    Edge: 139.0.3405.125
    Safari: 18.5
  npmPackages:
    @vitejs/plugin-react: ^4.4.1 => 4.5.2 
    vite: ^6.3.5 => 6.3.5 
    vite-plugin-dts: ^4.5.3 => 4.5.4

Validations

• Read the FAQ.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[qmhc]

Would you upgrade the version of node in your project?

[eparisio]

actually we can't, we have strict procedures for upgrading it that will require works of QA and intensive testing.
I know that the bug is not related directly to your library, but i report it because it is influenced by it, and as side effect all other projects that use it.
I'm opening a bug report to them too.