jfmengels/lib-upgrader

Install dependencies described in releases

Open

#2 opened on Apr 10, 2016

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (2 forks)github user discovery
enhancementhelp wanted

Repository metrics

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

Description

Follows the same train of though as #1.

I think it would be nice if in the provided releases array, we added support for additional dependencies to install (maybe even remove?).

[{
    "version": "0.14.0",
    "dependencies": [
        "react-dom@^0.14"
    ],
    "transforms": [
        "path/to/transorm/a.js",
        "path/to/transorm/b.js"
    ]
}]

For instance, in React v0.14, the module was split into two separate modules: react and react-dom. A similar thing happened with Babel v6.

Contributor guide

Research direction
Add an optional 'dependencies' field to the release objects in the releases configuration, and implement the logic to install them when running the upgrade.
Tech stack
javascript
Domain
cli
Issue type
Feature
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70