Option to use the `engine` value inside of package.json

Question

Option to use the `engine` value inside of package.json

aleccool213 opened this issue a year ago · comments

I see there is a legacy option for nvm files, what about engines["node"] inside of NPM projects package.json file? A lot of projects just have this set and nothing else. It is fully supported by NPM. If this is a good idea, I wouldn't mind making a PR to support it.

Jeff D. · Answer 1 · Wed May 10 2023 02:57:38 GMT+0800 (China Standard Time)

that field is for specifying compatible versions, it really shouldn't be used for this purpose IMO

Augusto Moura · Answer 2 · Wed May 10 2023 04:48:32 GMT+0800 (China Standard Time)

Agree with @jdxcode, aside from a differente semantic, engines allow much more than single versions, allowing full-fledge expressions (E.g.: 18 || 16 || 15.x), which are not planned at the moment.

Alec Brunelle · Answer 3 · Fri May 12 2023 20:54:20 GMT+0800 (China Standard Time)

Good to know! Thanks for the quick feedback.