yarn add @types/YYY@npm:@types/XXX does not work

[xaviergonz]

Do you want to request a feature or report a bug?
bug report

What is the current behavior?
When running the command I get
error Received malformed response from registry for undefined. The registry may be down.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

If the current behavior is a bug, please provide the steps to reproduce.
yarn add @types/material-ui-old@npm:@types/material-ui

What is the expected behavior?
It should install the current version of the @types/material-ui package as @types/material-ui-old

Please mention your node.js, yarn and operating system version.
node 8.4.0, yarn 1.0.1, win 10 x64

[BYK]

Hey @xaviergonz, thanks for the report! I'm having difficulty understanding what yarn add @npm: means. How is this used, is that a complete example? Can you give more details about what exactly are you running?

[xaviergonz]

Useful for when you want multiple versions of libraries in a project. eg. `yarn add lodash3@npm:lodash@^3 lodash4@npm:lodash@^4`. Basically it is used to create package aliases

[arcanis]

I kinda remember seeing @kittens mention a different syntax to do what you want, but I don't remember where.

[xaviergonz]

I just realized that markdown ate down all my @ characters the issue :) Fixed it

[rally25rs]

This sounds like we just don't support a command line syntax that NPM has. Marking this as a compatibility feature request.

[sheerun]

Here is different example that doesn't work:

yarn add next@npm:@sheerun/next@4.3.0-canary.8 --verbose

I'd like alias "next" as "@sheerun/next@4.3.0-canary.8"