wclr / yalc

Work with yarn/npm packages locally like a boss.
MIT License
5.64k stars 147 forks source link

package version dependent? #214

Open xenide opened 1 year ago

xenide commented 1 year ago

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.

wuelcas commented 1 year ago

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.