microsoft
[api-extractor] update of minmatch to v10+ breaks node compatibility <20
Summary
Hi, i'm here to report a recently update compatibility issue in the package imports, that breaks the compatibility with node under v20. 1 month ago the package @microsoft/api-extractor had update a minor version v7.52.10, where they update the minimatch package to v10.0.3, that remove the compatibility with node under v20. https://github.com/microsoft/rushstack/blob/main/apps/api-extractor/CHANGELOG.md#75210 https://github.com/isaacs/minimatch/blob/main/changelog.md#100
Details
There are some package out there that use the v7 version and generally if they are imported as "^7.xx.xx", they will automatically update to the most recent minor/patch version (for example one of the package that is using your dependancy is https://www.npmjs.com/package/vite-plugin-dts/v/5.0.0-beta.1), breaking all package at cascade while installing parents ones. In a minor version generally is not advisable to deprecate an entire set of node versions (<20), from v7.52.9 to v7.52.10
A solution, if possible, should be to revert the commit and upgrade to a more recent but with the same node compatibility as the old one or revert the change for v7 and create a v8 version of the plugin
Currently we cannot upgrade the node version as it would require in-depth testing and QA development by our client and costs that he would have to bear.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@microsoft/api-extractor version? |
v7.52.10 |
| Operating system? | Windows / Mac / Linux |
| API Extractor scenario? | |
| Would you consider contributing a PR? | No |
| TypeScript compiler version? | ~5.8.3 |
Node.js version (node -v)? |
18.18.2 |
