You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I do yalc link @project-foo/package1 in project-bar I can see the right files populated in the .yalc folder, however the project-bar/node_modules/@project-foo/package1 does not reflect the version in .yalc, but rather whatever existed before.
I have to manually delete the folder and create the symlink (usually have to cd down to make the symlink ../../.yalc/@project-foo/package1, possible because of #72 ?).
Shouldn't yalc link be doing this for me or am I missing something? If I do yalc add @project-foo/package1 --link this does create the symlink as expected, but adds the (unneeded) entry in package.json as well. Adding --pure doesn't touch package.json but then doesn't give me symlink either! 😅
The text was updated successfully, but these errors were encountered:
I have:
I can publish
@project-foo/package1
just fine.When I do
yalc link @project-foo/package1
inproject-bar
I can see the right files populated in the.yalc
folder, however theproject-bar/node_modules/@project-foo/package1
does not reflect the version in.yalc
, but rather whatever existed before.I have to manually delete the folder and create the symlink (usually have to
cd
down to make the symlink../../.yalc/@project-foo/package1
, possible because of #72 ?).Shouldn't
yalc link
be doing this for me or am I missing something? If I doyalc add @project-foo/package1 --link
this does create the symlink as expected, but adds the (unneeded) entry inpackage.json
as well. Adding--pure
doesn't touchpackage.json
but then doesn't give me symlink either! 😅The text was updated successfully, but these errors were encountered: