Running yarn link unlinks any modules linked via yarn link.

[chaddjohnson]

Yarn version 1.2.1.

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

Bug.

What is the current behavior?

Running yarn add [package-name] unlinks any linked modules. Here is a screenshot showing this:

If the current behavior is a bug, please provide the steps to reproduce.

cd app
ls -l node_modules | grep sequential --> shows that the module is not linked
yarn link sequential-ids
ls -l node_modules | grep sequential --> shows that the module is now linked
yarn add lodash
ls -l node_modules | grep sequential --> shows that the module is now unlinked

What is the expected behavior?

yarn add [package-name] should never cause linked packages to become unlinked.

Please mention your node.js, yarn and operating system version.

Node 8.6.0.

macOS High Sierra. This also happened on Sierra.

[wclr]

Right, before v1 yarn didn't touch symlinks in node_modules, but now when it performs some actions in node_modles it removes the symlinks of deps folders if it is not link: dependency and replaces it with version from the cache or local folder (if file: dep).

I'm not sure if it is by design behavior.

Also, want to mention yalc as an alternative to yarn link workflow and getting rid of symlinks.

[bestander]

@arcanis @BYK, raising this to your attention, looks like a noticeable regression.

[AlastairTaft]

Would be really useful for me if this one was fixed.

[chaddjohnson]

I understand this is fixed. Thank you. How can we test?

[wclr]

I understand this is fixed. Thank you. How can we test?

Clone master and build it, install using npm link, or wait for a release)