dylang/npm-check

Update peerDependencies along with devDependencies

Open

#130 opened on Apr 9, 2016

View on GitHub
 (4 comments) (12 reactions) (0 assignees)JavaScript (6,438 stars) (278 forks)batch import
enhancementhelp wantedwho else wants this?

Description

I :heart: npm-check, thank you! On a project that listed a package in both devDeps (for CI, local testing) and peerDeps, I noticed that npm-check only bumps the dependency in devDependencies and not in peerDependencies. Would be great to pair, like :chocolate_bar: and :wine_glass:.

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptnpmpackage.json structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests adding peerDependencies update alongside devDependencies in npm check. The relevant code is likely in the core update logic, possibly in files like `lib/check.js` or `lib/update.js`. A contributor should locate where devDependencies are currently updated and extend that code to handle peerDependencies. No additional maintainer comments or linked PRs are available.