Install fails with node v16.18.1 due to cheerio@1.0.0 dependency

[frazar]

Until last week, the package was successfully installing with Node v16.18.1, but now it fails.

$ yarn add vsts-coverage-styles@1.0.9
yarn add v1.22.22
info No lockfile found.
[1/4] Resolving packages...
warning vsts-coverage-styles > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vsts-coverage-styles > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[2/4] Fetching packages...
error cheerio@1.0.0: The engine "node" is incompatible with this module. Expected version ">=18.17". Got "16.18.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Reproduction steps:

$ echo "v16.18.1" > .nvmrc
$ cat .nvmrc
v16.18.1
$ fnm install
Installing Node v16.18.1 (x64)
$ node --version
v16.18.1
$ yarn --version
1.22.22
$ yarn add vsts-coverage-styles@1.0.9
yarn add v1.22.22
info No lockfile found.
[1/4] Resolving packages...
warning vsts-coverage-styles > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vsts-coverage-styles > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[2/4] Fetching packages...
error cheerio@1.0.0: The engine "node" is incompatible with this module. Expected version ">=18.17". Got "16.18.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

[davidsekar]

@frazar Since Azure DevOps have started supporting automated HTML file generation for code coverage report, I have stopped supporting or upgrading this extension.

Let me know, If you need it for a different reason. I can do the upgrade and support.

[frazar]

@davidsekar Thanks for your answer. The issue is not critical as I moved to more modern node version.