Yarn v2 link specific packages as it works in Yarn v1

[RuBAN-GT]

Hi everyone,

I have a simple scenario to create a symlink from node_modules to specific npm package directory as it works with npm link package_name or yarn link package_name (yarn v1) commands.
But as I understood properly, Yarn v2 has changes of this command behaviour (https://yarnpkg.com/cli/link) and creates resolutions at package.json.

Does somebody advice how to link packages as it was early?

Thank you!

[larixer]

There is no CLI command to create symlink in Yarn 2, but this behaviour is still supported. You can use link: protocol to achieve this behaviour:
https://yarnpkg.com/features/protocols
package.json

{
  "dependencies": {
    "my-package": "link:../relative/path/to/my-package"
  }
}

[r1y4h]

Yes, YARN_IGNORE_PATH=1 yarn link ...

Noobie question. What is YARN_IGNORE_PATH=1 I'm also on the same exact scenario as OP. We only need to use yarn link locally.

Is it run like this inside your pacakge.json script, example:

"link": "YARN_IGNORE_PATH=1 yarn link --private pacakge-1 "

[merceyz]

It will ignore the Yarn version specified by your project and invoke the global version (most likely v1) , but you should avoid doing that as much as possible. Use the yarn link and yarn unlink commands from v2/v3 instead

[r1y4h]

Thank you. yarn unlink still seems not available in v2.4.1. And just like what OP says, v1 link was the better choice for what we need as it doesn't alter any code files.

[merceyz]

yarn unlink still seems not available in v2.4.1

It's in the latest v3 RC

yarn set version berry && yarn set version canary

And just like what OP says, v1 link was the better choice for what we need as it doesn't alter any code files.

The v1 link wont install dependencies and doesn't work with PnP but if that's fine for you then feel free to use it

[r1y4h]

Yeah that's my original problem. I come here looking for why yarn link has changed and how it's intended to use now. Seems we have to adopt to the new yarn link now.