Lines Matching full:using
17 When not using Node-API, implementing addons is complicated,
67 using v8::FunctionCallbackInfo;
68 using v8::Isolate;
69 using v8::Local;
70 using v8::Object;
71 using v8::String;
72 using v8::Value;
106 When building addons with `node-gyp`, using the macro `NODE_GYP_MODULE_NAME` as
122 A context-aware addon can be constructed by using the macro
128 using namespace v8;
171 accomplished using the `new` keyword.
180 `v8::External` and makes it available in the native callback using the
192 using namespace v8;
255 * Be declared as context-aware using `NODE_MODULE_INIT()` as described above
268 down. If necessary, such hooks can be removed before they are run using
285 using node::AddEnvironmentCleanupHook;
286 using v8::HandleScope;
287 using v8::Isolate;
288 using v8::Local;
289 using v8::Object;
337 using a JSON-like format. This file is used by [node-gyp][], a tool written
355 use `node-gyp` directly can install it using the command
367 When using `npm install` to install a Node.js addon, npm uses its own bundled
387 locates addon modules, it is essentially using a `try…catch` pattern similar to:
412 * `node-gyp` can be run using the `--nodedir` flag pointing at a local Node.js
413 source image. Using this option, the addon will have access to the full set of
416 ### Loading addons using `require()`
458 set of APIs that are used by the native code. Instead of using the V8
470 // hello.cc using Node-API
512 Each of these examples using the following `binding.gyp` file:
533 built using `node-gyp`:
555 using v8::Exception;
556 using v8::FunctionCallbackInfo;
557 using v8::Isolate;
558 using v8::Local;
559 using v8::Number;
560 using v8::Object;
561 using v8::String;
562 using v8::Value;
565 // Input arguments are passed using the
592 // Set the return value (using the passed in
627 using v8::Context;
628 using v8::Function;
629 using v8::FunctionCallbackInfo;
630 using v8::Isolate;
631 using v8::Local;
632 using v8::Null;
633 using v8::Object;
634 using v8::String;
635 using v8::Value;
688 using v8::Context;
689 using v8::FunctionCallbackInfo;
690 using v8::Isolate;
691 using v8::Local;
692 using v8::Object;
693 using v8::String;
694 using v8::Value;
742 using v8::Context;
743 using v8::Function;
744 using v8::FunctionCallbackInfo;
745 using v8::FunctionTemplate;
746 using v8::Isolate;
747 using v8::Local;
748 using v8::Object;
749 using v8::String;
750 using v8::Value;
795 instances to be created using the JavaScript `new` operator:
804 using v8::Local;
805 using v8::Object;
857 using v8::Context;
858 using v8::Function;
859 using v8::FunctionCallbackInfo;
860 using v8::FunctionTemplate;
861 using v8::Isolate;
862 using v8::Local;
863 using v8::Number;
864 using v8::Object;
865 using v8::ObjectTemplate;
866 using v8::String;
867 using v8::Value;
980 creating object instances using the JavaScript `new` operator:
997 using v8::FunctionCallbackInfo;
998 using v8::Isolate;
999 using v8::Local;
1000 using v8::Object;
1001 using v8::String;
1002 using v8::Value;
1020 instantiating the object. This method takes the place of using `new` in
1062 using node::AddEnvironmentCleanupHook;
1063 using v8::Context;
1064 using v8::Function;
1065 using v8::FunctionCallbackInfo;
1066 using v8::FunctionTemplate;
1067 using v8::Global;
1068 using v8::Isolate;
1069 using v8::Local;
1070 using v8::Number;
1071 using v8::Object;
1072 using v8::String;
1073 using v8::Value;
1204 using v8::Context;
1205 using v8::FunctionCallbackInfo;
1206 using v8::Isolate;
1207 using v8::Local;
1208 using v8::Number;
1209 using v8::Object;
1210 using v8::String;
1211 using v8::Value;
1284 using node::AddEnvironmentCleanupHook;
1285 using v8::Context;
1286 using v8::Function;
1287 using v8::FunctionCallbackInfo;
1288 using v8::FunctionTemplate;
1289 using v8::Global;
1290 using v8::Isolate;
1291 using v8::Local;
1292 using v8::Object;
1293 using v8::String;
1294 using v8::Value;