Node.js & Git — Overview
What Node.js and Git are, how they fit together, and why you need both installed before you write a single line of code.
Before you can build anything — before you write your first line of React, before you connect to a database, before you deploy an app — two tools need to be on your computer.
Node.js. The engine that runs your code.
Git. The system that remembers every version of your code.
Everything else we install sits on top of these two. They are the foundation.
The Excel Analogy
You have spent years in Excel. You already understand both of these tools — you just didn't know it.
Node.js is the calculation engine inside Excel.
When you type =SUM(A1:A100) and press Enter, Excel doesn't display a formula — it runs it. There is an engine underneath Excel that reads your instruction, processes numbers, and returns a result. You never see this engine. You just type, and the result appears.
Node.js is that engine, but for JavaScript code. When you build a React app, your code is a set of instructions. Node.js is what reads and executes those instructions on your computer — and eventually, on servers all over the world. Without Node.js installed, your computer can't read or run any modern web application code.
Git is Excel's "Track Changes" — taken seriously.
Excel has a "Track Changes" feature. You've probably used it when a colleague reviews your work. It shows who changed what, when, and lets you accept or reject individual edits.
Git does the same thing, but for an entire project — every file, every change, tracked precisely and permanently. The difference is that Excel's Track Changes is an afterthought. Git is built specifically to do this job, and it does it completely. You can:
- Go back to any version of your project, from any point in time
- See exactly what changed between yesterday's version and today's
- Work on a separate "branch" so your experiments don't break the main version
- Merge contributions from multiple people without losing anyone's work
Git is not a nice-to-have. It is how all professional code is managed, everywhere, without exception.
How They Relate to Each Other
Node.js and Git are independent tools. Node.js doesn't know about Git, and Git doesn't know about Node.js. But you need both simultaneously on any real project:
| Node.js | Git |
|---|---|
| Runs your code | Tracks your code |
| Downloads and manages packages (libraries) | Saves snapshots of your entire project |
| Required to start your dev server locally | Required to push code to GitHub |
| Required by every JavaScript build tool | Required by every deployment pipeline |
The daily workflow: You write code in VS Code. Node.js runs that code locally so you can see it in your browser. Git saves a checkpoint of your progress. You push to GitHub, and it goes live on Vercel.
Every step in that chain depends on one or both of these tools.
Where They Fit in the Full Stack
| Layer | Tool | Depends on |
|---|---|---|
| Code editor | VS Code | Nothing |
| Engine to run code | Node.js | Nothing — installs standalone |
| Package manager | npm | Comes with Node.js automatically |
| Version control | Git | Nothing — installs standalone |
| React framework | Vite + React | Node.js + npm |
| Deployment | Vercel CLI | Node.js + npm + Git |
| AI assistant | Claude Code | Node.js |
Node.js and Git are at the base of the stack. Install them first.
What You'll Have After This Section
By the time you complete the pages in this section, you will have:
- Node.js 20 LTS installed on your machine, with
nodeandnpmavailable from any terminal - Git installed and recognized from the command line
- Git configured with your identity — your name and email on every change you make
- 10 core Git commands practiced and understood, with the Excel analogy for each
- A verification checklist you have run through and confirmed passes
Work through these pages in order. Node.js and Git are independent of each other, so you can install them in either order — but the page order here takes you from understanding to installation to configuration to practice, which is the clearest path.
Time Required
| Page | Estimated time |
|---|---|
| Why These Tools | 10 minutes reading |
| Node.js Installation | 10–15 minutes |
| Git Installation | 10–15 minutes |
| Git Configuration | 5 minutes |
| First Commands | 20–30 minutes (hands-on practice) |
| Verification | 5 minutes |
Total: approximately 60–75 minutes. Work at your own pace. If something doesn't look right, stop and check — don't rush past an error and hope it resolves itself. It won't.