fc28d9402f
This interface has long been unmaintained and doesn't match current best practices for C++ object management. It's also simply not a good idea to have this header be part of Node.js core; since it is an inline header, user code will depend on the Node.js version it was compiled with, and there is no way to adopt changes to this header independently of changing the target Node.js version. Better userland alternatives exist and have long been more popular, notably, `node-addon-api` and, for use cases where direct V8 API access is required, `nan`. Signed-off-by: Anna Henningsen <anna@addaleax.net> PR-URL: https://github.com/nodejs/node/pull/63756 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> |
||
|---|---|---|
| .. | ||
| addon-verify.mjs | ||
| deprecationCodes.mjs | ||
| generate-json-schema.mjs | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
Documentation Tooling
The Node.js API documentation tooling lives in nodejs/doc-kit. This module exists just to make it usable in Node.js core, any changes to the tooling should be done in that repository.