Chapter 5. Package Management
In Chapter 1, we briefly learned about Node’s default package manager, npm. It’s now time to take a deeper look and get comfortable finding, using, and creating packages for Node.
The term package is what the software world uses to describe a folder that contains code. In Node, that folder will also have a package.json file that describes the metadata and dependencies of the package.
The term module refers to a single file or a collection of related files that encapsulate a set of functionality. Modules allow developers to organize their code into separate and reusable units. A Node package often represents a single Node module, but some packages have more than one module.
A package usually refers to external code that a project depends on, but I think a better word to describe package code is generic. You can make pieces of your own code generic and extract them into a package that you can then use in many projects.
Introducing Package Management
If packages are just folders, why exactly do we need a package manager for them?
Keeping track of these package folders becomes challenging when there are many of them and when these packages depend on other packages. This is especially true for a team of developers working on the same Node project. Package management tools provide a simplified and systemic approach to handling the common tasks around packages. They provide simple commands to install, update, and remove packages, and to ensure that a project ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access