Owkay so I'm using node >10 to run packages that were designed for node 10 and more, and due to this change I can't install them anymore. How do we declare multiple compatible major versions in "engines", or is there a bypass switch ?

you have "engines": {"node": ">=10"} in package.json and it started failing?
Can you create a repo to reproduce?

Thanks, that indeed is the right syntax. :) (I meant by "I'm using node >10": "the version of node on my computer is strictly greater than 10")
I still have a need for packages that I don't own where the maintainer does not guarantee >11 compatibility to not have to install node 10 on my machine. Is there a bypass switch for this ?
If not, shouldn't we add one ?

Packages that you don't own? You mean dependencies inside node_modules? Those don't cause installations to fail unless you set the engine-strict config to true

Thanks for the quick answers! This behaviour is indeed mentionned in the documentation.
However I mean non-dependencies (a project workspace -~100 packages- I install using pnpm that is regularly updated so I can't just patch them everytime nor have them unclean in my git tree).

hm, I guess we can make this check a warning when engine-strict is false. But only the engines.node check

That would perfectly fit with my scenario! :)