0

I've had this issue for a long time and I'm finally done with it! I've got a single package in my app that, after each time yarn [install] is run it switches from the string version to the non-string version and vise versa in the yarn.lock file. If I check in the change and commit it, the next time I yarn, it switches back.

Here's the example

+ "ember-phone-input@github:cph/ember-phone-input#cph-modification":
- ember-phone-input@cph/ember-phone-input.git#cph-modification:

Anyone know of any settings to add to package.json do end this senseless psychic damage I'm taking

Luke
  • 2,053
  • 1
  • 18
  • 25
  • 1
    yarn@v1, unfortunately, is littered with bugs. Best thing you can do is migrate to something sensible like `yarn@v3` or `pnpm` – NullVoxPopuli Jan 13 '23 at 18:47

0 Answers0