N-API: npm package.json support for N-API versioning

[cjbj]

Is anyone working with the npm team to add package.json syntax to restrict installing a Node.js add-on only for a given (or greater) N-API ABI version? The engines specification can be seen as a partial solution, but isn't ideal.

[mhdawson]

We've not discussed that before, so quick answer is no.

It sounded like an interesting idea to the Node-API team. Are you interested in proposing to npm?

[cjbj]

@mhdawson I can open an issue. Is https:/npm/cli/issues the tracking system they are using now that https://npm.community/tags/c/bugs/cli/l/latest is closed? If you could add your weight and any useful technical information to the request, that would be helpful.

[mhdawson]

I'm not sure if issues is the right place or discussions. @darcyclarke what would you suggest?

[darcyclarke]

@cjbj this sounds like a good case for using our RFC process (ref. https:/npm/rfcs/ - or maybe create even an RRFC as an issue in that repo to test the waters/interest) - for reference, https:/npm/cli/issues has transitioned to only be intended for bugs in the npm CLI (we have other destinations for drive-by feature requests, questions etc.). In the interim of any net-new capability, engines is there - although it sounds like it's not ideal - and we will warn or throw depending on if a user defines --engines-strict

[cjbj]

I've opened npm/rfcs#369

Thanks @mhdawson and @darcyclarke

[mhdawson]

@cjbj thanks, commented there.