yarn resolutions map package does not work

[magicdawn]

as the doc says resolutons can map package
https://github.com/yarnpkg/rfcs/blob/master/implemented/0000-selective-versions-resolutions.md#mapping-version-specifications-as-well-as-packages-name

  "devDependencies": {
    "@angular/cli": "1.0.3",
    "typescript": "2.2.2"
  },
  "resolutions": {
    "typescript": "my-typescript-fork",
  }

this does not work on yarn(latest) 1.19.1, node 12
just a warning shows

warning Resolution field "<maped-package-name>" has an invalid version entry and may be ignored

[httpete]

We see the same on yarn 1.22.10 unfortunately.

[jdmeer]

The link you posted isn't really traditional documentation as much as it's a specification. The section you link to seems to be in the context of a discussion surrounding 'potential alternatives' which were not implemented at the time the doc was written. I came here hoping to find that they had later added it to the spec. No dice it seems 😥

[jodaka]

Too bad it doesn't work in real life. Would love to be able to temporary replace original packages with our forks.

[0xtomm]

Solution is to do:

  "devDependencies": {
    "@angular/cli": "1.0.3",
    "typescript": "2.2.2"
  },
  "resolutions": {
-    "typescript": "my-typescript-fork",
+    "typescript": "npm:my-typescript-fork",
  }

[undefined-moe]

This solution also causes a problem as yarn think this is a external url rather than a npm package, and when I execute yarn upgrade-interactive , It always gives this: (even no updates available)

Which is really annoying.