Episode 4: Packages and npm
Published Aug 20, 2026 · 8:53 · 7 comments
Packages let developers share their modules with the broader community. In this episode, you'll see how npm is used to install packages and to keep track of the dependencies your application depends on.

Show Notes
This episode uses Node.js v0.8.5; download and documentation links are provided below.
Links
- npm
- npm documentation (the same content as the npm help man pages)
- Semantic versioning
- npm documentation on dependency versions
Everyday npm Commands
- npm init – create a package.json file interactively
- npm install <package> – install a package into node_modules
- npm install <package> --save – install a package and save a dependency in package.json
- npm update <package> – update a package to the latest version allowed by the version specification in package.json
- npm outdated – show packages that have versions newer than the one installed that are allowed by the version specification in package.json
- npm ls – see all packages your package depends on
Comments







Frequently Asked Questions
Copyright © 2012 Brandon Tilley
Node.js is an official trademark of Joyent. This site is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
Once you're comfortable with the basics, the same npm workflow scales to larger projects: package.json records what your app needs, node_modules holds the installed code, and commands like npm update, npm outdated, and npm ls help you keep dependencies current and visible. Pairing that workflow with semantic versioning gives you a predictable way to decide when a newer release is safe to adopt.