Table of Contents
You followed the instructions. Node.js is installed. Terminal is open. Then the next line says run npm install and you stop. What is NPM? What is it installing? Where does it go? Why does every tool require this?
That confusion is exactly what this post fixes.
Understanding what is a package manager is the piece that makes the entire modern development ecosystem make sense. Once you get it, the instructions stop feeling random and start feeling logical.
I hit this exact wall when I was setting up Claude Code for the first time. Nobody explained what a package manager actually was. They just told me to run commands. This post is what I needed back then.
What Is a Package Manager, Really?
A package manager is a tool that automatically downloads, installs, updates, and removes software packages for you.
A package is just a bundle of code that does something specific. It could be a tool, a library, a plugin, or a utility. Instead of finding that code yourself, downloading a zip file, extracting it, placing it in the right folder, and configuring it manually, a package manager does all of that with one command.
You type the command. The package manager handles everything else. The right version gets downloaded. It goes to the right place. Any other packages that it depends on get installed automatically too.
The One Sentence Version
A package manager is like an app store for your terminal. You tell it what you want. It handles the download, installation, and setup automatically.
This is why understanding what is a package manager matters so much for anyone building with AI tools today. Every AI development environment, every JavaScript framework, every build tool you will encounter gets installed and managed through a package manager. It is not a detail. It is the mechanism behind everything.
The App Store Analogy That Makes It Click
Think about how you install an app on your phone. You open the App Store or Google Play. You search for what you want. You tap install. The store handles the download, the installation, the permissions, everything. You just tap one button.
A package manager does exactly the same thing but for developer tools and code libraries, and instead of tapping a button you type a command in the terminal.
The app store knows where every app lives, what version is current, and what it needs to run. The package manager knows the same things about every software package. You ask for something by name. It knows where to get it, which version is stable, and what else needs to come with it.
The difference is that an app store manages apps for regular users. A package manager manages code packages for builders. Once you understand that parallel, everything about what a package manager does becomes obvious.
What Is a Package Manager Used For?
Once you understand what is a package manager in concept, the practical uses become clear immediately.
Installing tools and libraries
When I installed Claude Code, the command was npm install -g @anthropic-ai/claude-code. That one line told NPM to download Claude Code, install it globally on my machine, and make it available from any terminal window. No manual download. No folder management. One command.
Managing versions
Package managers track exactly which version of every package is installed in your project. This matters because a tool that works with version 3.0 of a library might break with version 4.0. The package manager locks the versions so your project always uses what it was built with.
Handling dependencies automatically
Most packages depend on other packages to work. When you install one thing, it might need 20 other things. The package manager figures all of that out and installs everything in the right order without you having to know any of it.
Updating everything at once
Instead of manually checking every tool for updates, a package manager can check and update all installed packages with a single command. Your entire development environment stays current without hunting down individual downloads.
Sharing project setups
When you share a project with someone else, you do not send all the installed packages. You send a file called package.json that lists everything the project needs. The other person runs one command and the package manager installs everything automatically. Clean and consistent every time.
NPM: The Package Manager You Already Have
If you followed the previous post in this series and installed Node.js, you already have a package manager installed. It came with Node.js automatically. It is called NPM, which stands for Node Package Manager.
NPM is the default package manager for the JavaScript ecosystem and the one you will use most often when working with AI tools. It has access to over 2 million packages through the NPM registry, which is the largest software registry in the world.
What The NPM Registry Is
Think of the NPM registry as the warehouse. Every package ever published for Node.js lives there. When you run npm install, NPM goes to that warehouse, finds exactly what you asked for, and brings it back to your project. You can read more about it at docs.npmjs.com.
There are other package managers in the JavaScript world. Yarn and pnpm are two popular alternatives. They do the same job as NPM but with different performance characteristics and features. For beginners working with AI tools, NPM is the right choice. It is what Claude Code expects. It is what Remotion uses. It is the standard.
You can verify NPM is installed by opening your terminal and running npm -v. If you see a version number, you are ready. If you need to install Node.js first, check out the previous post in this series.
What Are Dependencies and Why Do They Matter?
Every time you install a package, it might require other packages to function. Those required packages are called dependencies.
Here is a real example from my own work. When I scaffolded a Remotion video project using npx create-video@latest, the package manager installed 301 packages automatically. I asked for one thing. The package manager figured out the 300 other things that one thing needed and installed all of them without me having to know any of their names.
How Dependencies Work
Without a package manager, installing something like Remotion would mean manually downloading 301 separate packages, figuring out the right versions of each one, and placing them all in the right locations. No serious developer would do this manually. The package manager makes it one command.
5 Package Manager Commands You Will Actually Use
These are the NPM commands that show up constantly when working with AI tools. Learn these five and you can handle almost everything.
npm install
Installs all dependencies listed in the project’s package.json file. Run this when you clone or download an existing project for the first time. It sets up everything the project needs.
npm install package-name
Installs a specific package and adds it to your project. Replace package-name with whatever you actually want. Example: npm install remotion
npm install -g package-name
The -g flag means global. Installs the package on your entire machine instead of just one project. This is how Claude Code gets installed — globally so you can run it from any terminal window anywhere.
npm run dev
Starts the development server for a project. This is the command that opens your Remotion preview at localhost:3000. The word dev is a script defined in the project’s package.json file.
npm -v
Checks which version of NPM is installed. Run this to confirm your package manager is working before you try to install anything else. If it returns a version number, you are ready to go.
The Bottom Line
What is a package manager? It is the tool that handles installing, updating, and managing software packages so you do not have to do any of it manually. It is the app store for your terminal.
NPM is the package manager that comes with Node.js. It is what powers the installation of Claude Code, Remotion, and virtually every JavaScript-based AI tool that exists right now. When an instruction tells you to run npm install, you are using a package manager to set up everything your project needs in one step.
This post is part of THE BLUEPRINT series on Practical AI Builds. If you have not read the earlier posts, start with what is terminal and then what is Node.js. The three posts together give you the full foundation for working with AI development tools.
Terminal. Node.js. Package manager. That is the stack. Everything else builds on top of it.
[convertkit form=9252938]About The Author
Damisi Harris is the founder of Clickbox Media Studio and the creator of Practical AI Builds. At 52 with no coding background, he documents every real build, every real mistake, and every real breakthrough on this site and on the Becoming The Architect YouTube channel. Follow the build: @Mr_ClickBoxStudio