Repository navigation
Node API core consolidation #44071
Description
Activity
I am interested in working on this
Reacted by Chengzhong Wu@deepakrkris it will be great if you can help out on this! As we discussed in the last node-api team meeting, please free feel to drop a comment on the document if you have any questions.
- added a commit that references this issue
on Dec 19, 2022 - added a commit that references this issue
on Jan 1, 2023 - added 2 commits that reference this issue
on Jan 4, 2023 - added a commit that references this issue
on Jan 26, 2023 @legendecas maybe we should go through this in the next node-api meeting to see what's been completed and what is still needed on this one.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.- moved this from Need Triage to Done in Node-API Team Project
on Jul 26, 2026
People are complaining that the node-api core implementation is deviating from node.js core conventions and has a lot of workarounds and non-conventional mechanisms, especially around the finalizers. It makes it harder to maintain the node-api code base.
I'm working with the @nodejs/node-api team on the document https://docs.google.com/document/d/1Bqm05PWQni65FVdSKiaVAkqCAOD9HIfCqG_Y4CAYTbo/edit?usp=sharing to list the problems we are facing and try to figure out what approaches we can apply.
@addaleax thanks for bringing the topic up at #36510 (comment).
Opening this issue to track the progress.