Getting started with Node.js & npm

JavaScript was originally designed to run only inside web browsers. Node.js changed that — it lets you run JavaScript anywhere: on your laptop, on a server, or inside tools like build systems and development servers.

Today, Node.js is essential for modern web development. Here's what it powers:

• •Running development servers locally (e.g. Next.js, Vite)
• •Building and bundling front-end applications
• •Running back-end APIs and server-side logic
• •Scripting, automation, and command-line tools

1. Go to nodejs.org and click the LTS download button.
2. Run the .msi installer — the default options work fine for most users.
3. Open a new Command Prompt or PowerShell window when done.

Using Windows? See Pro Tip #1 to set up Git Bash as your default IDE terminal.

npm (Node Package Manager) is how you add libraries to your projects. Instead of writing everything from scratch, you can install packages that other developers have built and shared.

npm install lodash

npm install --save-dev typescript

npm install -g vercel

When you install a package, npm adds it to a file called package.json, which tracks all the dependencies your project needs. Anyone who clones your project can run npm install to get the exact same packages.

Packages themselves are downloaded into a node_modules folder. You never need to edit this folder — npm manages it for you, and it's typically excluded from version control via .gitignore.

The npmjs.com is the public website where all npm packages are listed. You can search for packages, read their documentation, and check their popularity.

When evaluating a package, look for these signals:

• •Weekly downloads — More downloads usually means it's widely trusted and actively used.
• •Version number — A version above 1.0 suggests it's considered stable by its maintainers.
• •Dependencies — Fewer dependencies means less risk of breaking changes.
• •README & docs — Good documentation is a sign of a well-maintained package.

Try searching from the command line:

npm search react

Let's create a new project folder and initialize it with npm:

mkdir my-first-project && cd my-first-project

npm init -y

Now install your first package — let's use chalk, a popular library for adding color to terminal output:

npm install chalk

Notice that your package.json now lists chalk as a dependency, and a node_modules folder has appeared.

When you use an AI coding agent like Google Antigravity, GitHub Copilot, or Cursor, it can automatically install npm packages as needed. If the agent needs a library to accomplish a task, it will run npm install for you.

Here's what you should know about how agents use npm:

• •Agents prefer popular, well-maintained libraries over writing custom code from scratch — this means fewer bugs and better compatibility.
• •You can ask the agent to use a specific package, or let it choose the best one for the task.
• •All packages the agent installs are recorded in your package.json, so you always have visibility into what was added.
• •If the agent installs something you don't want, you can remove it with npm uninstall <package-name>.

Here's a quick reference of commands you'll use frequently:

Now that you have Node.js set up, here are some great next steps: