Commit 4c1f85b
doc: revise addons introduction for brevity and clarity
PR-URL: #30756
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 1c452f0 commit 4c1f85b
1 file changed
Lines changed: 3 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3,10 +3,9 @@ | |||
| 3 | 3 | <!--introduced_in=v0.10.0--> | |
| 4 | 4 | <!-- type=misc --> | |
| 5 | 5 | ||
| 6 | - Node.js Addons are dynamically-linked shared objects, written in C++, that | ||
| 7 | - can be loaded into Node.js using the [`require()`][require] function, and used | ||
| 8 | - just as if they were an ordinary Node.js module. They are used primarily to | ||
| 9 | - provide an interface between JavaScript running in Node.js and C/C++ libraries. | ||
| 6 | + Addons are dynamically-linked shared objects written in C++. The | ||
| 7 | + [`require()`][require] function can load Addons as ordinary Node.js modules. | ||
| 8 | + Addons provide an interface between JavaScript and C/C++ libraries. | ||
| 10 | 9 | ||
| 11 | 10 | There are three options for implementing Addons: N-API, nan, or direct | |
| 12 | 11 | use of internal V8, libuv and Node.js libraries. Unless you need direct | |
0 commit comments