The short answer
Check provenance, version, license and maintenance. Small features do not always require another package.
Try it in three steps
- Ask which specific gap a new dependency solves.
- Check whether existing or standard capabilities suffice.
- Keep version locks and an installation record.
A practice prompt
Before you start
Compare approaches without installing packages.
Practice material (fictional)
Task: count characters in a short passage on a page. Options: existing browser code or a new large framework.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Does this feature require a new dependency? Compare an existing-tool approach, package source and maintenance impact before installing.What to look for (not a recorded test result)
Check existing capabilities first. A dependency needs a concrete added benefit and maintenance rationale, not a professional-looking label.
If it goes wrong
For missing-package errors, check project directory and manifest before installing globally.
Check your result
You know what was added, why it is needed and how installation is reproduced.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.