Development dependency
A development dependency is a software package needed for development tasks such as building, testing, or debugging, but not normally needed for an application's runtime operation.
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
A development dependency is a software package required for developing, testing, or building an application but not necessarily for running it in production.
- How it is used
- Separates development and testing tools from packages needed to run a production microservice.
- How deep it goes
- Explains npm installation flags and package.json grouping, then applies the distinction to development and production Dockerfiles.
- Examples
- Uses nodemon for live reload and Jest for tests, contrasting both with the production MongoDB library.
- What you can do after
- Apply it using npm to classify packages and omit development dependencies from production installations.
Web Components in Action
A development dependency is a software package required for developing, testing, or building an application but not normally required at runtime.
- How it is used
- Separates development, testing, and build tooling from packages needed by the running application.
- How deep it goes
- Explains classification, local installation, package.json recording, and script execution without detailing npm dependency resolution.
- Examples
- Uses Rollup for bundling and Web Component Tester with Mocha, Babel, and plugins for component testing and builds.
- What you can do after
- Operate/configure npm projects by installing tools locally and invoking repeatable build or test scripts.
Read how Web Components in Action explains development dependency →
Pro Angular 16
The devDependencies property is an npm manifest field listing packages required during development but excluded from the finished application.
- How it is used
- Separates development, build, and testing tools from packages required to run the finished application.
- How deep it goes
- Defines the manifest distinction, shows representative packages, and demonstrates installation with npm, but does not detail dependency-resolution internals.
- Examples
- Uses Angular CLI, TypeScript, Jasmine, Karma, and deployment server packages as concrete devDependencies.
- What you can do after
- Operate NPM to install development-only packages and identify tooling that belongs in devDependencies.
Fast by Default
A development dependency is a package required for development activities such as testing, linting, or debugging but not for runtime execution.
- How it is used
- Separates development tooling from packages required during runtime and keeps production installations smaller.
- How deep it goes
- Defines the category and gives an npm production-install command, but does not detail manifest configuration or lifecycle behavior.
- Examples
- Uses npm ci --omit=dev and npm ls --all to illustrate production exclusion and dependency inspection.
- What you can do after
- Operate npm to inspect dependencies and install production packages without development dependencies.
Secrets of the JavaScript Ninja, Third Edition
A project dependency needed for development activities such as building and testing, but not normally at application runtime.
- How it is used
- Separates project tools used during development from packages needed at application runtime.
- How deep it goes
- Explains the package.json distinction and clarifies how npm handles transitive development dependencies.
- Examples
- Uses the TypeScript compiler and Prettier as tools installed for development work.
- What you can do after
- Operate/configure npm project tooling by installing packages with --save-dev and recording them under devDependencies.
Read how Secrets of the JavaScript Ninja, Third Edition explains development dependency →
Essential TypeScript 5, Third Edition
devDependencies is the package.json field that records packages required during project development rather than at application runtime.
- How it is used
- Separates project tools from packages included in the application, while deployment configurations may use it for container-support packages.
- How deep it goes
- Explains package classification, local installation, version ranges, and commands, but does not detail NPM's dependency-resolution algorithm.
- Examples
- Uses tsc-watch and typescript listings plus Angular and React container configurations with Express-related packages.
- What you can do after
- Operate/configure NPM projects by classifying packages and installing local development tools with --save-dev.
Read how Essential TypeScript 5, Third Edition explains development dependency →
Also covered in
What to know first
- packageA software package is a named unit that groups related software components, either for organization and compilation or for distribution and reuse.
- package.jsonpackage.json is the standard JSON manifest for an npm or Node.js package, declaring metadata, dependencies, scripts, entry points, and related configuration.
- dependencyA dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.
Related concepts
- cargo.tomlpart of · Cargo.toml is a TOML-formatted manifest file that declares a Rust package’s metadata, dependencies, targets, and build configuration.
- production dependencycontrasts with · A production dependency is a software package or component required by an application in its deployed runtime environment.
- Jestconfigures · Jest is a JavaScript testing framework for defining, running, and asserting automated tests.
- packageconfigures · A software package is a named unit that groups related software components, either for organization and compilation or for distribution and reuse.
- package.jsonpart of · package.json is the standard JSON manifest for an npm or Node.js package, declaring metadata, dependencies, scripts, entry points, and related configuration.
Questions about development dependency
What is development dependency?
A development dependency is a software package needed for development tasks such as building, testing, or debugging, but not normally needed for an application's runtime operation.
Which Manning books explain development dependency?
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform, Web Components in Action, Pro Angular 16, Fast by Default, Secrets of the JavaScript Ninja, Third Edition and Essential TypeScript 5, Third Edition.
What should I know before learning development dependency?
Manning books that teach development dependency usually introduce package, package.json, Java and dependency first.
What is the difference between development dependency and production dependency?
A development dependency is a software package needed for development tasks such as building, testing, or debugging, but not normally needed for an application's runtime operation. A production dependency is a software package or component required by an application in its deployed runtime environment.
What is development dependency part of?
Development dependency is part of cargo.toml. Cargo.toml is a TOML-formatted manifest file that declares a Rust package’s metadata, dependencies, targets, and build configuration.
What is development dependency also called?
Development dependency is also called dev dependency or devDependencies.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





