1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
# Setup
## Prerequisites
Before starting to use **Node-API** you need to assure you have the following
prerequisites:
* **Node.JS** see: [Installing Node.js](https://nodejs.org/)
* **Node.js native addon build tool**
- **[node-gyp](node-gyp.md)**
## Installation and usage
To use **Node-API** in a native module:
1. Add a dependency on this package to `package.json`:
```json
"dependencies": {
"node-addon-api": "*",
}
```
2. Decide whether the package will enable C++ exceptions in the Node-API
wrapper, and reference this package as a dependency in `binding.gyp`.
The base ABI-stable C APIs do not throw or handle C++ exceptions, but the
Node-API C++ wrapper classes may _optionally_
[integrate C++ and JavaScript exception-handling
](https://github.com/nodejs/node-addon-api/blob/HEAD/doc/error_handling.md).
To use without C++ exceptions, add the following to `binding.gyp`:
```gyp
'dependencies': [
"<!(node -p \"require('node-addon-api').targets\"):node_addon_api",
],
```
To enable that capability, add an alternative dependency in `binding.gyp`
depending on if you want to integrate C++ exception handling for exceptions
derived from `Napi::Error` or all C++ exceptions. To catch only
`Napi::Error` exceptions, use:
```gyp
'dependencies': [
"<!(node -p \"require('node-addon-api').targets\"):node_addon_api_except",
],
```
Or, to allow catching all native C++ exceptions, use the
`node_addon_api_except_all` dependency:
```gyp
'dependencies': [
"<!(node -p \"require('node-addon-api').targets\"):node_addon_api_except_all",
],
```
If you decide to use node-addon-api without C++ exceptions enabled, please
consider enabling node-addon-api safe API type guards to ensure the proper
exception handling pattern:
```gyp
'dependencies': [
"<!(node -p \"require('node-addon-api').targets\"):node_addon_api_maybe",
],
```
3. If you would like your native addon to support OSX, please also add the
following settings in the `binding.gyp` file:
```gyp
'conditions': [
['OS=="mac"', {
'cflags+': ['-fvisibility=hidden'],
'xcode_settings': {
'GCC_SYMBOLS_PRIVATE_EXTERN': 'YES', # -fvisibility=hidden
}
}]
]
```
4. Include `napi.h` in the native module code.
To ensure only ABI-stable APIs are used, DO NOT include
`node.h`, `nan.h`, or `v8.h`.
```C++
#include "napi.h"
```
At build time, the Node-API back-compat library code will be used only when the
targeted node version *does not* have Node-API built-in.
The `NODE_ADDON_API_DISABLE_DEPRECATED` preprocessor directive can be defined at
compile time before including `napi.h` to skip the definition of deprecated
APIs.
By default, throwing an exception on a terminating environment (eg. worker
threads) will cause a fatal exception, terminating the Node process. This is to
provide feedback to the user of the runtime error, as it is impossible to pass
the error to JavaScript when the environment is terminating. The
`NODE_API_SWALLOW_UNTHROWABLE_EXCEPTIONS` preprocessor directive can be defined
to bypass this behavior, such that the Node process will not terminate.
Various Node-API constructs provide a mechanism to run a callback in response to
a garbage collection event of that object. These callbacks are called
[_finalizers_]. Some finalizers have restrictions on the type of Node-APIs
available within the callback. node-addon-api provides convenience helpers that
bypass this limitation, but may cause the add-on to run less efficiently. The
`NODE_ADDON_API_REQUIRE_BASIC_FINALIZERS` preprocessor directive can be defined
to disable the convenience helpers.
[_finalizers_]: ./finalization.md
|
