Software Dependencies Explained: The Other Code Your Website Uses

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: A dependency supplies other code

   0:18

   A project can use a package to provide a needed feature.

   On-screen labels: Reusable package; Required feature; Project dependency.

2. 2

   Step 2: The package has an identity

   0:30

   Its name and version identify the intended component.

   On-screen labels: Package name; Package version; Project declaration.

3. 3

   Step 3: Dependencies can have their own

   0:42

   One package may rely on additional packages in turn.

   On-screen labels: Direct dependency; Further dependencies; Dependency tree.

4. 4

   Step 4: Development tools count too

   0:54

   Build tools and testing tools can be dependencies of the project.

   On-screen labels: Build tooling; Testing tooling; Runtime code.

5. 5

   Step 5: Updates need review

   1:06

   Check maintenance, compatibility and relevant security information.

   On-screen labels: Maintainer guidance; Release notes; Compatibility checks.

6. 6

   Step 6: Keep a reproducible project

   1:18

   Retain the dependency declarations and relevant lockfile for handover.

   On-screen labels: Project declaration; Relevant lockfile; Setup instructions.

Common questions

Go further