As of a year or so ago, there is an npm module weak-napi (https://github.com/node-ffi-napi/weak-napi), which is API-compatible with this module and claims a couple of advantages, including (a) avoiding crashes, and (b) having better binary compatibility by using N-API. Based on my own use of weak-napi, it seems like (a) is indeed true.
Especially since this module seems to have been effectively abandoned, I would like to suggest that @TooTallNate cede the module name in npm to @node-ffi-napi, so that the latter can publish weak-napi as v2.0 of weak.
As of a year or so ago, there is an npm module
weak-napi(https://github.com/node-ffi-napi/weak-napi), which is API-compatible with this module and claims a couple of advantages, including (a) avoiding crashes, and (b) having better binary compatibility by using N-API. Based on my own use ofweak-napi, it seems like (a) is indeed true.Especially since this module seems to have been effectively abandoned, I would like to suggest that @TooTallNate cede the module name in npm to @node-ffi-napi, so that the latter can publish
weak-napias v2.0 ofweak.