alanshaw/david

Outdated status should respect supported node versions

Open

#95 opened on Dec 28, 2015

View on GitHub
 (3 comments) (1 reaction) (0 assignees)JavaScript (81 forks)batch import
help wanted

Repository metrics

Stars
 (962 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Here is an example explaining the issue.

  • foo supports node version >= 0.10.0
  • foo depends on version 1.x.x of bar
  • bar version 2.0.0 is published and supports node version => 4.0.0
  • bar version 1.0.0 supports node version >= 0.10.0

David shouldn't show an outdated badge for foo, since foo is using the latest supported version of bar on the version of node that foo runs on.

Either that, or David should have an updated status for this special case.

Contributor guide

Research direction
Investigate how David determines outdated badges and how it compares supported Node versions between dependencies. Look at the logic for version range resolution and check if it considers the semver range of the parent package's node engine requirement.
Tech stack
javascriptnodejs
Domain
toolingdevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptNode.jsnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70