Check and show engine requirements (if there is one in package.json)

[GeoffreyParrier]

Clear and concise description of the problem

Currently we don't know if a package will be compatible with our current version of node on update.

Suggested solution

A new column with a copy of the engines.node field if it is defined in the package.json of each dependency.

Maybe make it clear if a dependency don't have a value with a "N/A" or something like this.

Alternative

No response

Additional context

Some idea extending this request:

• A command to list current engines.node of each dependencies
• A command to check if a node version (current by default) is compatible with our dependencies

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[antfu]

That would be cool! Would you like to draft a PR for it? Thanks

[GeoffreyParrier]

Absolutely, I need to find some time for it but I would be happy to help, no promises though, so if someone want to take charge of this, it's fine for me too

[GeoffreyParrier]

@antfu Do you think it would be ok if I make a PR to update fast-npm-meta to handle package.json engines too ?

[antfu]

Yeah sure, please!