Suggest an editImprove this articleRefine the answer for “What are dev dependencies and how do they differ from regular dependencies?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Dev dependencies (**`devDependencies`**)** are packages needed **only during development**, not required for the application to run in production. **Regular dependencies (**`dependencies`**)** are packages the application **needs at runtime**, that is, directly while it is running. **Key point:** dev dependencies are usually not installed in production, to shrink the environment and speed up deployment.Shown above the full answer for quick recall.Answer (EN)Image**Dev dependencies (**`devDependencies`**)** are packages needed **only during development**, not required for the application to run in production. **Regular dependencies (**`dependencies`**)** are packages the application **needs at runtime**, that is, directly while it is running. --- ### The core difference | Type | Where it's used | Examples | |---|---|---| | `dependencies` | while the application runs | `react`, `axios`, `express` | | `devDependencies` | only during development and build | `webpack`, `eslint`, `jest`, `babel` | --- ### The practical difference 1. **Regular dependencies are installed on the production server too**, because the application won't start without them. 2. **Dev dependencies are usually not installed in production**, in order to: - shrink the size of the environment, - speed up deployment, - leave out extra tools that aren't needed there. --- ### How they are installed - A regular dependency: ```bash npm install react ``` - A dev dependency: ```bash npm install webpack --save-dev ``` --- **In short:** `dependencies` is what the application needs to run. `devDependencies` is what only the developer needs during development and build.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.