Review requested:

• @nodejs/gyp
• @nodejs/node-api

I'm wondering whether it makes sense to limit the use of SharedArrayBuffer for security reasons. For example, if I define and restrict kMaxSharedArrayBufferSize, it seems like a good way to improve application security — because if a very large and malicious data is received, it could potentially consume the user's memory.

Codecov Report

❌ Patch coverage is 70.27027% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.90%. Comparing base (fc4a8af) to head (54c9b03).
⚠️ Report is 139 commits behind head on main.

@@            Coverage Diff             @@
##             main   #59071      +/-   ##
==========================================
- Coverage   90.09%   89.90%   -0.20%     
==========================================
  Files         645      655      +10     
  Lines      189930   192858    +2928     
  Branches    37217    37808     +591     
==========================================
+ Hits       171125   173385    +2260     
- Misses      11512    12032     +520     
- Partials     7293     7441     +148     

@mertcanaltin , thank you for adding the new APIs for the shared buffer!
Please follow the same naming conventions, versioning, and other rules as you did for the new Node-API functions that you added before. E.g. using node_api_ prefix, using experimental version, etc.
See: https://github.com/nodejs/node/blob/main/doc/contributing/adding-new-napi-api.md

@mertcanaltin , thank you for adding the new APIs for the shared buffer! Please follow the same naming conventions, versioning, and other rules as you did for the new Node-API functions that you added before. E.g. using node_api_ prefix, using experimental version, etc. See: https://github.com/nodejs/node/blob/main/doc/contributing/adding-new-napi-api.md

I forgot about this, sorry, updating immediately

Thank you for Rewiev I have made the arrangements @legendecas

Overall LGTM, thank you for working on this

You are welcome