A Walk Through Electron's Internals
summary
Covers how Electron assembles Chromium, Node and V8 into a desktop runtime: Libchromium content is patched per Chrome release (patches must be reapplied for each stable update), Node is rebuilt from source because of a chromium v8 mismatch, and Brightray hosts Chromium for cross‑platform builds. Shows concrete plumbing: native node bindings expose APIs, IPC links browser vs renderer processes, ASAR is a read‑only archive that monkey‑patches fs, demos confirm the process isolation and that the build/patch workflow is tedious but functional.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:36Brennan Foster
- 1:21What Makes Up Electron
- 3:38Api Stability
- 4:03Electron Atom Io
- 5:17Upgrading Electron
- 6:56Chromium Source
- 15:32Build Electron from Scratch
- 20:57Setup of the Code
- 22:01Message Loops
- 22:30Atom Browser Main Parts
- 24:01Libuv Event Loop
- 26:04Atom Bindings
- 31:12Demo App
- 33:20Dev Dependency
- 34:23Initializing Electron
- 34:36Api Exports
- 36:54Adam Binder
- 39:13Binding Behavior
- 44:25Web Contents Api
related talks
58mCross-Platform Desktop Apps with Electron
22mBuilding Desktop Applications with Node and Electron
48mGetting Started with Electron
29mAPI Modernization: Building Bridges As You Cross Them
24mElectron: The Event Loop Tightrope
32mFelix Rieseberg - SeattleJS Conference 2017
26mNode on the Desktop: Building Apps with Electron v1
27mBuilding Cross Platform Desktop Apps With Electron