การทำงานกับโมดูลเนทีฟ

Welcome! Today we'll explore Native Modules in Electron. These are special Node.js modules written in C or C++.

Think of them as powerful extensions that let your JavaScript code interact directly with the operating system at a lower level or perform high-speed computations.

Native modules are used for specific, critical tasks:

• Performance: For CPU-intensive operations that JavaScript might struggle with.
• Low-level OS Access: Interacting with hardware or specific operating system features not exposed by Node.js or Electron's standard APIs.
• Existing C/C++ Libraries: Reusing established, optimized C/C++ libraries directly within your Electron app.

Electron uses Node.js internally. This means any Node.js native addon (a C/C++ module compiled for Node.js) can also be used in your Electron application.

You'll typically load these modules in the main process, as it has full Node.js API access, and then expose necessary functions to the renderer process via IPC or preload scripts (covered in later lessons).

To build native modules, you need a few tools installed on your system:

• Python: Version 2.7 (for node-gyp).
• C/C++ Compiler: Like Visual Studio (Windows), Xcode Command Line Tools (macOS), or build-essential (Linux).
• node-gyp: A cross-platform command-line tool written in Node.js for compiling native addon modules.

node-gyp is crucial for native module development. It takes configuration files (binding.gyp) and uses them to generate platform-specific build files (like Makefiles or Visual Studio projects).

This allows your C/C++ code to be compiled correctly for your operating system and Node.js version, producing a .node file that Node.js (and Electron) can load.

A native module project typically includes:

• C/C++ source files: Your core logic.
• binding.gyp: A configuration file for node-gyp, specifying how to compile your C/C++ code.
• package.json: Defines your module and its dependencies.

The compilation process turns your C/C++ code into a .node file, which is essentially a shared library.

When you install an npm package that contains a native module, npm automatically runs node-gyp rebuild for you.

This command compiles the native code for your specific Node.js and Electron version, creating the .node file in a directory like ./build/Release/ or ./build/Debug/.

Once compiled, a native module can be loaded into your Electron application using the standard Node.js require() function.

You simply point to the compiled .node file. This is usually done in your Electron's main process, or in a preload script for the renderer process if you need to expose its functionality there securely.

Here's how you would use a hypothetical native module in your Electron application's JavaScript code. We'll simulate its functionality for this runnable example.

Which of the following is NOT a primary reason to use Electron native modules?

Great job! You've learned about Node.js native modules in Electron:

• They are C/C++ code compiled to .node files.
• Used for performance, OS interaction, and C/C++ library integration.
• node-gyp is the key tool for compilation.
• They are loaded using require() in JavaScript.

Next, we'll look at creating Tray Applications and Badges, another way to leverage native features!