Electron Desktop App Development · 课时

理解 Electron 的架构

清晰理解 Electron 如何结合 Chromium 和 Node.js，以及主进程与渲染器进程如何协同工作，然后再构建更大型的应用。

理解 Electron 的架构 是 CoddyKit 上的免费 Electron Desktop App Development 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Electron Desktop App Development 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Electron Desktop App Development 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Two Worlds in One App

Electron fuses two runtimes: Chromium for the UI and Node.js for system access. Grasping how they coexist is the foundation of every app.

The Main Process

Each app has exactly one main process. It runs your entry file, controls the lifecycle, and creates BrowserWindow instances with full Node access.

const { app, BrowserWindow } = require('electron');
app.whenReady().then(() => {
  new BrowserWindow({ width: 800, height: 600 });
});

The Renderer Process

Each window runs its own renderer process — basically a Chromium tab rendering HTML, CSS, and JavaScript like any web page.

Why Separate Processes?

Separate processes buy you stability and security: one window crashing won't kill the app, and the UI can't freely poke the OS.

Chromium's Role

Chromium is the same engine as Chrome. It handles rendering, layout, and the DOM, keeping your app consistent across platforms.

Node.js's Role

Node.js brings the file system, networking, and npm packages into your app — the part that makes Electron more than just a browser.

const os = require('os');
console.log('Platform:', os.platform());
console.log('CPUs:', os.cpus().length);

The Event Loop

The main process shares Node's event loop. Long synchronous work freezes the UI, so reach for async patterns instead.

setTimeout(() => console.log('runs later'), 0);
console.log('runs first');

Process Communication Preview

Main and renderer are in separate memory spaces; they talk through IPC (inter-process communication). You will dive into it later.

The package.json Entry

Electron finds the main process file via the main field in package.json. The snippet below shows the minimal entry config.

{
  "name": "my-app",
  "main": "main.js",
  "scripts": { "start": "electron ." }
}

Cross-Platform Promise

Write once, run on Windows, macOS, and Linux. Electron bundles the runtime, so users never need a browser installed.

Putting It Together

It all loops together: the main process boots, makes a window, the renderer loads your page, and IPC links them — the heartbeat of every app.

Quick Check

Confirm your understanding of Electron processes.

Recap

You've got the architecture: one main process (Node.js) driving multiple renderer processes (Chromium), connected by IPC for safe desktop apps.

常见问题解答

「理解 Electron 的架构」课时是免费的吗？

是的 — 「理解 Electron 的架构」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Electron Desktop App Development 课程的其余内容，请升级到 CoddyKit PRO。 Electron Desktop App Development 课程共包含 4 节课。

「理解 Electron 的架构」这节课中我会学到什么？

清晰理解 Electron 如何结合 Chromium 和 Node.js，以及主进程与渲染器进程如何协同工作，然后再构建更大型的应用。你通过在浏览器中直接运行的动手代码来练习 Electron Desktop App Development，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Electron Desktop App Development 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Electron Desktop App Development 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「理解 Electron 的架构」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Electron Desktop App Development 课中编写并运行代码吗？

能。每节 Electron Desktop App Development 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Electron Desktop App Development