In the release-it package for example, we would like to support any future Node version under the package's Node engines:

• feat: add support for newer node versions release-it/release-it#1182

Motivation: This makes it easier for consumers to install / run / test the package under all the latest / supported Node versions, without depending on every package to release an update to expand the range forward every six months.

This causes an error from installed-check:

Errors:

ava: Narrower "engines.node" is needed: ^18.18.0 || ^20.9.0 || ^22.0.0

Suggestions:

Combined "engines.node" needs to be narrower: ^18.18.0 || ^20.9.0 || ^22.0.0

Is there any way to disable this error? Does it make sense for us to disable this check? Are we using installed-check appropriately? Should the default behavior be relaxed?

Related:

• Add option to only enforce lower version bound? #101