liveBook · Manning

Development dependency

As explained in Fast by Default

A development dependency is a package required for development activities such as testing, linting, or debugging but not for runtime execution.

A development dependency supports activities such as testing, linting, or debugging but is unnecessary for runtime execution. Excluding it from production deployments reduces installed application size. section 8.2.2

Manage development dependencies by:

  • Inspecting the complete dependency tree to identify development packages and duplicated versions. section 8.2.2
  • Auditing unexpectedly large packages before replacing or removing them. section 8.2.2
  • Running npm ci --omit=dev for production deployments so development-only packages are not installed. section 8.2.2
npm ls --all

Use npm ls --all to inspect the full dependency tree and trace packages that may be unnecessary for production. section 8.2.2

How Fast by Default covers it

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.
How it connects
Connects development dependencies with dependency analysis, package size, dependency trees, and production deployment.

Also explained in

Compare how 6 books explain development dependency →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.