Hi @mk-pmb 👋,
Thanks for the PR and for adding the link to the npm documentation for the engines.node field! It's a helpful addition.

I did notice the phrasing:

"If volta.node isn't defined, then it will look for engines.node (as defined here in the npm docs)."

The reference to "as defined here in the npm docs" could be a little misleading. While the npm docs do describe how to use the engines.node field, they don’t explain the behavior of checking volta.node before engines.node.

It might be clearer to adjust the wording slightly to specify that the npm docs only define how engines.node is used, without implying they describe the full behavior of checking volta.node first.

Looking forward to your thoughts! 😊

Good catch! That could indeed be confusing. I updated the branch to insert a new line below the original,

(The latter is defined here in the npm docs.)