I'm working on an app that relies on a dependency we also manage. I use yarn link to tell my app to use the local dependency and all this worked well with my recent changes. (I did not increment the version number of the dependency).
Then another team member carried out some work on the same dependency, bumped the version number from 0.4.0 to 0.5.0 and pushed to our develop branch. All test passed, HUZZAH!
I pulled this update and merged to my feature branch and yarn build and I can confirm that the changes are present. I then adjusted my app's package.json to look for the new 0.5.0 version, delete the node_modules folder and yarn install to get the update but yarn keeps throwing up it cannot find version 0.5.0 and then lists all previous versions available.
I have wasted hours on this and I have no idea why this is happening, has anyone seen this before and have a solution?
question from:
https://stackoverflow.com/questions/65852150/yarn-link-not-picking-up-local-dependency-version-change 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…