@@ -16,15 +16,15 @@ provided by Node.js when using C++. It provides a C++ object model
16
16
and exception handling semantics with low overhead.
17
17
18
18
There are three options for implementing addons: Node-API, nan, or direct
19
- use of internal V8, libuv and Node.js libraries. Unless there is a need for
20
- direct access to functionality which is not exposed by Node-API as outlined
19
+ use of internal V8, libuv, and Node.js libraries. Unless there is a need for
20
+ direct access to functionality that is not exposed by Node-API as outlined
21
21
in [ C/C++ addons] ( https://nodejs.org/dist/latest/docs/api/addons.html )
22
22
in Node.js core, use Node-API. Refer to
23
23
[ C/C++ addons with Node-API] ( https://nodejs.org/dist/latest/docs/api/n-api.html )
24
24
for more information on Node-API.
25
25
26
26
Node-API is an ABI stable C interface provided by Node.js for building native
27
- addons. It is independent from the underlying JavaScript runtime (e.g. V8 or ChakraCore)
27
+ addons. It is independent of the underlying JavaScript runtime (e.g. V8 or ChakraCore)
28
28
and is maintained as part of Node.js itself. It is intended to insulate
29
29
native addons from changes in the underlying JavaScript engine and allow
30
30
modules compiled for one version to run on later versions of Node.js without
@@ -46,7 +46,7 @@ provides an [ABI stability guide][] containing a detailed explanation of ABI
46
46
stability in general, and the Node-API ABI stability guarantee in particular.
47
47
48
48
As new APIs are added to Node-API, node-addon-api must be updated to provide
49
- wrappers for those new APIs. For this reason node-addon-api provides
49
+ wrappers for those new APIs. For this reason, node-addon-api provides
50
50
methods that allow callers to obtain the underlying Node-API handles so
51
51
direct calls to Node-API and the use of the objects/methods provided by
52
52
node-addon-api can be used together. For example, in order to be able
@@ -56,7 +56,7 @@ APIs exposed by node-addon-api are generally used to create and
56
56
manipulate JavaScript values. Concepts and operations generally map
57
57
to ideas specified in the ** ECMA262 Language Specification** .
58
58
59
- The [ Node-API Resource] ( https://nodejs.github.io/node-addon-examples/ ) offers an
59
+ The [ Node-API Resource] ( https://nodejs.github.io/node-addon-examples/ ) offers an
60
60
excellent orientation and tips for developers just getting started with Node-API
61
61
and node-addon-api.
62
62
@@ -195,7 +195,7 @@ To run the **node-addon-api** tests with `--debug` option:
195
195
npm run-script dev
196
196
```
197
197
198
- If you want faster build, you might use the following option:
198
+ If you want a faster build, you might use the following option:
199
199
200
200
```
201
201
npm run-script dev:incremental
@@ -223,7 +223,7 @@ See [benchmark/README.md](benchmark/README.md) for more details about running an
223
223
224
224
As node-addon-api's core mission is to expose the plain C Node-API as C++
225
225
wrappers, tools that facilitate n-api/node-addon-api providing more
226
- convenient patterns on developing a Node.js add-ons with n-api/node-addon-api
226
+ convenient patterns for developing a Node.js add-on with n-api/node-addon-api
227
227
can be published to NPM as standalone packages. It is also recommended to tag
228
228
such packages with ` node-addon-api ` to provide more visibility to the community.
229
229
0 commit comments