Gabriel Schulhof
Gabriel Schulhof
Our README.md already advocates the use of badges. Let's encourage the use of npm/github tags for packages using N-API/node-addon-api. That way, the addons using the tags would be more discoverable,...
> Sometimes you may wish to trigger garbage collection sooner in order to make finalizer callbacks to be called. This will not necessarily be guaranteed, although attempting it can nevertheless...
> A suggestion is a new N-API function to create custom exotic objects (like Proxy in JavaScript, but without the extra checking). Re: https://github.com/nodejs/node/issues/14256
Please have a look at https://docs.google.com/forms/d/1BlVwIYZPBBmR46Ru3okvddLiPj5Zy03XPE2kyW55VzQ/edit because it contains a list of the benchmarks we have. Please inform us as to how often you used each of them last year!
Related issues: https://github.com/npm/npm/issues/12133 https://github.com/npm/normalize-package-data/issues/75 This package also [makes the assumption](https://github.com/npm/read-package-json/blob/336a212716bb830781d7e71580adaeda377b69d9/read-json.js#L138) that the presence of a preinstall script means that the package does not use a gyp file and that the...
https://github.com/npm/normalize-package-data/blame/master/lib/normalize.js#L25-L29 Why is this assumption being made? It results in https://github.com/npm/npm/issues/12133
`new Buffer(...)` is deprecated and unsafe. It appears in the code in [these places](https://github.com/bitpay/bitcore-lib/search?q=%22new+Buffer%22&unscoped_q=%22new+Buffer%22). Can it be moved to `Buffer.from(...)`?
The example should also illustrate the use of `napi_make_callback`. Re: https://github.com/nodejs/node/issues/14256
In our ObjectWrap N-API examples we store the `napi_ref` returned from `napi_wrap()` in the native object instance although we never use it. To `napi_delete_reference()` in the destructor we need to...