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 publish changes, it seems that unless I also upgrade the version number in package.json, the existing version that is consumed downstream doesn't change (even when I do a yalc update). Is this the intended behavior?
However the strange thing is that we can observe the hash change in yalc.sig in node_modules/, but the behavior doesn't change unless I update the version number.
The text was updated successfully, but these errors were encountered:
I have the same issue. I solved this by using yalc link instead of yalc add in the project I want to use my local package. Then when I make changes to my local package I run yalc push --scripts --replace --changed (I use the scripts flag so the build script gets executed) and my project picks up the changes and recompiles.
When I publish changes, it seems that unless I also upgrade the version number in
package.json
, the existing version that is consumed downstream doesn't change (even when I do ayalc update
). Is this the intended behavior?However the strange thing is that we can observe the hash change in
yalc.sig
innode_modules/
, but the behavior doesn't change unless I update the version number.The text was updated successfully, but these errors were encountered: