Most software projects are assembled from useful building blocks: a framework, a database client, a chart library, a testing tool, a deployment tool. A package manager fetches those building blocks, records their versions, and installs them in a repeatable way.

You do not need to become a package-manager expert. You do need to understand the difference between installing something on your computer and installing something inside one project.

Two kinds of installation

Homebrew is a common Mac package manager. winget is common on Windows. npm and pnpm are common package managers for JavaScript projects. They solve different layers of the same problem.

Computer package managerInstall tools: Git, Node, VS CodeProject package managerInstall project dependenciesRun the application

The project manifest is the receipt

In many web projects, package.json is the file that names the project's dependencies and scripts. A lock file records the precise versions selected. These files let another computer—or an AI agent—recreate the same environment.

Do not casually delete or hand-edit them because they look technical. Ask the agent what a proposed dependency does, why it is needed, and whether it creates a new cost, license, or security responsibility.

A careful install conversation

Before approving an install, ask:

1. Is this a computer-wide tool or project-only dependency? 2. What problem does it solve? 3. Is there already a tool in the project that solves it? 4. What files will change? 5. How will we verify it works?

Good request:

Do not confuse installation with configuration

An installed package is not necessarily a working feature. A database client may also need a URL, an authentication provider may need credentials, and a chart library may need data and a component that uses it. AI agents often move quickly from “we need this package” to “it is installed.” Make them complete the thought: what configuration is required, where do the values come from, which environment uses them, and how will we test the integration without exposing secrets?

This distinction will save you from a common beginner problem: a project builds successfully but the new service still does nothing because the required connection was never configured.

Practical exercise

Open a project's manifest file with VS Code. Ask the AI to group its dependencies into: framework, UI, data, testing, and tooling. Do not install anything. Learn to read the project's receipt before changing it.

Check your understanding

1. What is the difference between a computer tool and a project dependency? 2. What file often records JavaScript project dependencies? 3. Why do lock files matter? 4. What should you ask before approving an AI-proposed installation?