Gabriel Schulhof
Gabriel Schulhof
https://github.com/nodejs/node/pull/25539 proposes an ABI checking scheme.
@mhdawson can we add a field to our top-level CI job that would cause it to append `--debug` to the npm test command line that runs our tests?
Spreadsheet tracking relative importance of benchmarks: https://docs.google.com/spreadsheets/d/17ey-6r_sTVYpy6Zv0n55kqkVgqRf67aaf6Ub7eebGgo/edit#gid=0
... and the survey: https://docs.google.com/forms/d/1BlVwIYZPBBmR46Ru3okvddLiPj5Zy03XPE2kyW55VzQ/edit
Here's a spreadsheet with the processed responses where the benchmarks are sorted in order of popularity: https://docs.google.com/spreadsheets/d/1_7VrAFO8K9KdQW8qEmnKnVBb514SMRqYiitoDu_cMiM/edit#gid=979605
https://github.com/MayhemYDG/iltorb/tree/napi documents a slight memory leak wrt. V8 bindings.
https://github.com/MayhemYDG/iltorb/pull/70#issuecomment-397127385
We discussed a possible solution to the accumulation of native finalizers during a tight loop that creates wrapped objects here: https://github.com/nodejs/node-addon-api/issues/1140
@cjihrig in the event of a libuv-2.0 release, is there danger of the polling API suffering an ABI break?
This is the extent to which we use `wrapper_` and `env_`: https://github.com/nodejs/node-addon-examples/blob/dc86a662c27c5732e069e1c19d3b7a8e74e86d29/6_object_wrap/napi/myobject.cc#L6-L11 and https://github.com/nodejs/node-addon-examples/blob/dc86a662c27c5732e069e1c19d3b7a8e74e86d29/6_object_wrap/napi/myobject.cc#L72-L78