Anyone using npm link/yarn link successfully for developing local libraries?

I want to have library auto-building in one terminal and used in another project seamlessly after every file change.I'm a bit surprised to discover exactly the same problem with npm and yarn -- after installing new packages, symlinked packages disappear.npm issue - http://ift.tt/2xmeSiD issue - 1214, 3288Do you put linked libs in package.json or just run npm link? How do you use linking? Are you having the same problems? Any easy workarounds?Thanks

Submitted September 22, 2017 at 11:59AM by Madd0g