Gecko [ unitednationsplay.com ]

Name	Size	Permission	Date
contributing	[ DIR ]	drwxr-xr-x	2022-01-26 16:43
doc_img	[ DIR ]	drwxr-xr-x	2022-01-26 16:43
adding-new-napi-api.md	2.55 KB	-rw-r--r--	2022-01-10 13:06
backporting-to-release-lines.md	4.38 KB	-rw-r--r--	2022-01-10 13:06
building-node-with-ninja.md	1.42 KB	-rw-r--r--	2022-01-10 13:06
collaborator-guide.md	40.27 KB	-rw-r--r--	2022-01-10 13:06
commit-queue.md	5.4 KB	-rw-r--r--	2022-01-10 13:06
cpp-style-guide.md	12.79 KB	-rw-r--r--	2022-01-10 13:06
diagnostic-tooling-support-tiers.md	8.66 KB	-rw-r--r--	2022-01-10 13:06
doc-style-guide.md	5.72 KB	-rw-r--r--	2022-01-10 13:06
internal-api.md	539 B	-rw-r--r--	2022-01-10 13:06
investigating_native_memory_leak.md	26.95 KB	-rw-r--r--	2022-01-10 13:06
maintaining-V8.md	17.66 KB	-rw-r--r--	2022-01-10 13:06
maintaining-c-ares.md	1.63 KB	-rw-r--r--	2022-01-10 13:06
maintaining-icu.md	8.27 KB	-rw-r--r--	2022-01-10 13:06
maintaining-npm.md	1.2 KB	-rw-r--r--	2022-01-10 13:06
maintaining-openssl.md	3.82 KB	-rw-r--r--	2022-01-10 13:06
maintaining-root-certs.md	3.57 KB	-rw-r--r--	2022-01-10 13:06
maintaining-the-build-files.md	2.39 KB	-rw-r--r--	2022-01-10 13:06
maintaining-zlib.md	892 B	-rw-r--r--	2022-01-10 13:06
node-postmortem-support.md	2.53 KB	-rw-r--r--	2022-01-10 13:06
offboarding.md	727 B	-rw-r--r--	2022-01-10 13:06
releases.md	34.1 KB	-rw-r--r--	2022-01-10 13:06
security-release-process.md	5.99 KB	-rw-r--r--	2022-01-10 13:06
strategic-initiatives.md	2.93 KB	-rw-r--r--	2022-01-10 13:06
technical-values.md	2.77 KB	-rw-r--r--	2022-01-10 13:06
using-internal-errors.md	4.9 KB	-rw-r--r--	2022-01-10 13:06
using-symbols.md	2.31 KB	-rw-r--r--	2022-01-10 13:06
writing-and-running-benchmarks.md	22.76 KB	-rw-r--r--	2022-01-10 13:06
writing-tests.md	15.83 KB	-rw-r--r--	2022-01-10 13:06

Rename

# Contributing a new API to Node-API

Node-API is the next-generation ABI-stable API for native modules.
While improving the API surface is encouraged and welcomed, the following are
a set of principles and guidelines to keep in mind while adding a new
Node-API.

* A new API **must** adhere to Node-API API shape and spirit.
  * **Must** be a C API.
  * **Must** not throw exceptions.
  * **Must** return `napi_status`.
  * **Should** consume `napi_env`.
  * **Must** operate only on primitive data types, pointers to primitive
    data types or opaque handles.
  * **Must** be a necessary API and not a nice to have. Convenience APIs
    belong in node-addon-api.
  * **Must** not change the signature of an existing Node-API API or break
    ABI compatibility with other versions of Node.js.
* New API **should** be agnostic towards the underlying JavaScript VM.
* New API PRs **must** have a corresponding documentation update.
* New API PRs **must** be tagged as **n-api**.
* There **must** be at least one test case showing how to use the API.
* There **should** be at least one test case per interesting use of the API.
* There **should** be a sample provided that operates in a realistic way
  (operating how a real addon would be written).
* A new API **should** be discussed at the Node-API team meeting.
* A new API addition **must** be signed off by at least two members of
  the Node-API team.
* A new API addition **should** be simultaneously implemented in at least
  one other VM implementation of Node.js.
* A new API **must** be considered experimental for at least one minor
  version release of Node.js before it can be considered for promotion out
  of experimental.
  * Experimental APIs **must** be documented as such.
  * Experimental APIs **must** require an explicit compile-time flag
    (`#define`) to be set to opt-in.
  * Experimental APIs **must** be considered for backport.
  * Experimental status exit criteria **must** involve at least the
    following:
    * A new PR **must** be opened in `nodejs/node` to remove experimental
      status. This PR **must** be tagged as **n-api** and **semver-minor**.
    * Exiting an API from experimental **must** be signed off by the team.
    * If a backport is merited, an API **must** have a down-level
      implementation.
    * The API **should** be used by a published real-world module. Use of
      the API by a real-world published module will contribute favorably
      to the decision to take an API out of experimental status.
    * The API **must** be implemented in a Node.js implementation with an
      alternate VM.