Expose version property in public API #1479
Merged
+24
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a proposal to expose the package
version
property in the public API.The
version
value is already used by the conversion tooling and is additionally useful in external contexts too, for example when specifying/detectingnode-addon-api
as an optional and/or peer dependency.This would bring
node-addon-api
in line withnode-gyp
, which already exportsrequire('node-gyp').version
. The change in the PR will allow me to improve the install-time detecting/logging fornode-addon-api
withinsharp
.It also adds a test with expectations for this property as well as all existing exported properties.