What Is a Package Manager? Installing and Tracking Website Dependencies

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: Start with the package list

   0:18

   The project declares the packages it needs.

   On-screen labels: Required packages; Project declaration; Version requirements.

2. 2

   Step 2: A manager installs the packages

   0:30

   It retrieves suitable package versions for the project.

   On-screen labels: Package source; Installed files; Resolved versions.

3. 3

   Step 3: A registry stores packages

   0:42

   The manager can retrieve packages from a configured registry.

   On-screen labels: Package registry; Package metadata; Configured source.

4. 4

   Step 4: A lockfile records the resolution

   0:54

   Where used, it records the dependency tree for repeatable installs.

   On-screen labels: Resolved versions; Dependency tree; Repeatable installation.

5. 5

   Step 5: Updates can change behaviour

   1:06

   Review the proposed update and test the resulting project.

   On-screen labels: Release notes; Compatibility; Working build.

6. 6

   Step 6: Document the expected tool

   1:18

   Include the package manager and setup steps in the handover.

   On-screen labels: Expected manager; Setup instructions; Maintainer guidance.

Common questions

Go further