Getting Started with Node.js
This article belongs to the Node.js course, which is actively in development with new lessons rolling out regularly.
Ready to write your first piece of server-side JavaScript? This guide will walk you through setting up a Node.js project, creating your entry file, and understanding how Node executes your code.
Creating Your First Node.js Project
Step 1: Initialize a Node Project
Open your terminal and run the following commands to create a new directory and initialize your project:
mkdir node-app
cd node-app
npm init -y # This creates a package.json file, which stores project metadata and dependencies.
Note: The npm init -y command automatically creates a package.json file with default settings, which acts as the blueprint for your project, storing metadata and dependencies. When you install external packages later, they will be stored locally inside a node_modules folder.
Step 2: Create the Entry File
Create a new file named index.js in your project root and add a simple console.log statement:
// index.js
console.log("Hello, Node.js!");
Step 3: Run Your Code
Execute your file from the terminal using the Node runtime:
node index.js
Note: In Node.js, each file is treated as an independent module with its own local scope, preventing variables from leaking globally (unlike traditional browser JavaScript).
How Node Executes your Code
- Runtime Initialization: Node.js fires up its core components, initializing the V8 engine to handle code execution and libuv to manage asynchronous operations and the event loop.
- File Loading: Node reads your target JavaScript file from the file system.
- Parsing and Compilation: V8 parses the source code and compiles it into native machine code.
- Execution: The script starts running. Synchronous code executes immediately.
- Lifecycle Management:
- If your script only contains synchronous code (like a simple console.log), the program exits automatically when no more work remains.
- If your script creates an HTTP server, opens a database connection, or sets timers (setTimeout), the Event Loop stays active, keeping your application running and listening for incoming requests.