| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 27e7976 commit 36a8af7
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -15,7 +15,7 @@ Refer to [C/C++ Addons with N-API](n-api.html) for more information on N-API. | |||
| 15 | 15 | When not using N-API, implementing Addons is complicated, | |
| 16 | 16 | involving knowledge of several components and APIs: | |
| 17 | 17 | ||
| 18 | - * V8: the C++ library Node.js currently uses to provide the | ||
| 18 | + * V8: the C++ library Node.js uses to provide the | ||
| 19 | 19 | JavaScript implementation. V8 provides the mechanisms for creating objects, | |
| 20 | 20 | calling functions, etc. V8's API is documented mostly in the | |
| 21 | 21 | `v8.h` header file (`deps/v8/include/v8.h` in the Node.js source | |
@@ -418,7 +418,7 @@ dramatically from one V8 release to the next (and one major Node.js release to | |||
| 418 | 418 | the next). With each change, Addons may need to be updated and recompiled in | |
| 419 | 419 | order to continue functioning. The Node.js release schedule is designed to | |
| 420 | 420 | minimize the frequency and impact of such changes but there is little that | |
| 421 | - Node.js can do currently to ensure stability of the V8 APIs. | ||
| 421 | + Node.js can do to ensure stability of the V8 APIs. | ||
| 422 | 422 | ||
| 423 | 423 | The [Native Abstractions for Node.js][] (or `nan`) provide a set of tools that | |
| 424 | 424 | Addon developers are recommended to use to keep compatibility between past and | |
| Back | FazBrowse Home | New Git URL |
0 commit comments