Open OmarJaroudi opened 1 year ago
Hi @OmarJaroudi!
This is not an issue with yalc
itself but more precisely with the link:
protocol.
The list of Yarn supported protocols: https://yarnpkg.com/features/protocols
From what we can see, the link protocol doesn't follow package dependencies. Meaning that if we link to a package, the package dependencies won't actually be installed.
This is solved by the portal
protocol - which should work in the exact same way as link
but it actually installs the dependencies of the link.
I made a PR to support portal
: https://github.com/wclr/yalc/pull/219
Hello,
I want to use
yalc add <package> --link
but I noticed that the original dependencies of the package I'm consuming are being dropped after I runyarn install
So if myyarn.lock
file originally looked likeAfter running
yalc add --link
the entry for that package in myyarn.lock
file looks likeAs such, I end up missing some dependencies needed by
my-local-package
and cannot start my consumer app.Any ideas if there is a way past this? Ideally to ensure that the dependencies of a yalc'd package are installed while using --link.
I'm using
link
instead of the classicfile
because I don't want to have to runyarn install
every time I push changes tomy-local-package
.link
allows me to pick up changes on reload