Node.js: Code Outside the Browser / Node.js Internals and How it Works

Node, V8 and C++

🎯 Goal of This Note

Understand what Node.js is actually built from — the underlying libraries and dependencies that make it work as a server-side JavaScript runtime. 🧠

🏗️ Node.js Is Built on Dependencies

Node.js itself is essentially a combination of several key libraries working together. The two most important are:

  1. ⚡ V8 Engine

  2. 🔄 libuv

⚡ 1. The V8 Engine

  • 🚀 Node.js is a JavaScript runtime built on top of Google's V8 engine.

  • ⚙️ V8's job: converts JavaScript code into machine code that a computer's processor can actually execute.

  • ❌ Without V8, Node would have no way of understanding or running JavaScript code at all — it's a completely fundamental building block of Node's architecture.

💡 V8 alone, however, is not enough to build a full server-side framework — it only handles turning JS into machine code, not things like file access or networking.

🔄 2. libuv

libuv is an open-source library with a strong focus on asynchronous I/O (input/output).

🛠️ What libuv Provides

  • 🖥️ Access to the underlying operating system — including:

    • 📁 The file system

    • 🌐 Networking

    • ⚙️ Other OS-level features

  • ✨ Implements two of the most important features in Node.js:

    1. 🔁 The Event Loop

    2. 🧵 The Thread Pool

🔄 Event Loop vs. 🧵 Thread Pool (Brief Overview)

Component

Handles

🔄 Event Loop

"Easy," lightweight tasks — executing callbacks, handling network I/O

🧵 Thread Pool

"Heavier" work — file access, compression, and other CPU/resource-intensive tasks

📖 These two concepts will be explained in much greater detail in upcoming lectures — this is just an introduction to what libuv is responsible for.

⚠️ Node.js Isn't "Just JavaScript"

  • 💻 libuv is written in C++, not JavaScript.

  • ⚡ V8 (the JS engine) also relies on C++ internally.

  • ✅ Conclusion: Node.js is actually a mix of C++ and JavaScript under the hood — not pure JavaScript.

🎨 The Magic: Abstraction

  • 🤝 Node.js wraps all that C++ machinery and exposes it to you through plain JavaScript.

  • ✍️ You write JavaScript only — e.g. fs.readFile() — while C++ code in libuv does the real work behind the scenes.

  • 🙌 You never touch C++ yourself.

💡 Without this abstraction layer, building server apps would mean writing C++ directly — far harder and less accessible.

📚 Other Supporting Libraries in Node.js

Besides V8 and libuv, Node also depends on several other specialized libraries:

Library

Purpose

🌐 http-parser

Parsing HTTP data

🔍 c-ares (or similar)

Handling certain DNS-related requests

🔒 OpenSSL

Cryptography (used for security-related operations, like HTTPS)

📦 zlib

Compression

💡 These libraries are less critical to deeply understand at this stage — they're mentioned mainly for completeness, to show the full picture of what Node.js is built from.

🧩 Putting It All Together

When all these pieces — ⚡ V8, 🔄 libuv, 🌐 http-parser, 🔍 c-ares, 🔒 OpenSSL, 📦 zlib, and others — are combined, the result is Node.js: a runtime ready to be used for building real-world, server-side applications. 🚀