[FEATURE] Create RFC for Yarn Resolutions

[karlhorky]

What / Why

Not sure if this is the right way to do this, but I wanted to create a placeholder issue for the eventual creation an RFC for Yarn Resolutions.

As @isaacs mentioned in #39 (comment) (emphasis mine):

I think a pretty good plan is maybe to ratify this, de-ratify the current overrides, and instead add a new RFC to implement yarn's resolutions with the same syntax and logic as yarn uses. Better to walk the existing cowpath than create another one.

References

• Original Package Overrides RFC (accepted): Package overrides #27
• New Package Overrides RFC (now abandoned) package.json overrides option #39
• Newer acceptDependencies RFC acceptDependencies package.json field #72
• Related "Multi Target Proposal" RFC: Multi target proposal #28
• Yarn Resolutions: https://yarnpkg.com/lang/en/docs/selective-version-resolutions/

[ruyadorno]

Putting this back on the agenda since I think we might want to close it given that #72 was ratified and implemented.

[karlhorky]

Oh nice, an acceptDependencies field! In which version of npm can I use this?

Does this cover common cases of Yarn Resolutions? For example:

1. I want to upgrade all versions of minimist at any level to version 0.2.1:

{
  "resolutions": {
    "minimist": "0.2.1"
  }
}

It looks like acceptDependencies covers this use case.

2. I want to upgrade minimist to 0.2.1, but only when it's a dependency of mkdirp. In other cases, I want to use version 1.2.5.

{
  "resolutions": {
    "**/mkdirp/minimist": "0.2.1",
    "mkdirp": "1.2.5"
  }
}

I'm not sure whether acceptDependencies would cover this common case.

These are just a couple that I have dealt with a lot. Maybe @arcanis could chime in with other common use cases for Resolutions.

---

Taking a look at the example of acceptDependencies, it's not immediately clear to me whether anything other than the most simple case is supported:

{
    "name": "my-node4-package",
    "engines": {
        "node": ">=4"
    },
    "dependencies": {
        "make-dir": "^1.3.0"
    },
    "acceptDependencies": {
        "make-dir": "2.x - 3.x"
    }
}