You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With node-pre-gyp and prebuild, the N-API version is essentially specified by the user and then the actual N-API version being built against is communicated into the binding.gyp file using a new napi-build-version variable we created for the purpose.
In the linked issue, the user is requesting that node-gyp inform the binding.gyp file which N-API version is supported by the version of Node being built against.
It's like the opposite of what we implemented for node-pre-gyp and prebuild.
Activity
jschlight commentedon May 14, 2019
With
node-pre-gypandprebuild, the N-API version is essentially specified by the user and then the actual N-API version being built against is communicated into thebinding.gypfile using a newnapi-build-versionvariable we created for the purpose.In the linked issue, the user is requesting that
node-gypinform thebinding.gypfile which N-API version is supported by the version of Node being built against.It's like the opposite of what we implemented for
node-pre-gypandprebuild.richardlau commentedon May 23, 2019
A PR was opened against core: nodejs/node#27800
NickNaso commentedon May 23, 2019
Hi everyone,
I closed my previous PR and reopened new one nodejs/node#27835. Please if you have time take a look.
NickNaso commentedon Jun 7, 2019
Hi everyone,
if someone has time could take a look at this PR nodejs/node#27835 in particular the last two comments? I need a feedback.
build: expose napi_build_version variable
build: expose napi_build_version variable
build: expose napi_build_version variable
NickNaso commentedon Jul 3, 2019
I’m closing this because the PR has been landed yesterday and the work now is on Node.js 12.6.0
build: expose napi_build_version variable