See https://github.com/yarnpkg/yarn/issues/5240.
I'm not optimistic either party will resolve this. We might need to generate a preinstall script that prevents you from running npm when the project has yarn.lock and vice versa.
Sorry, I thought I was being helpful :( I was hoping we could figure this out alright. :< :< :<
You totally were! Sorry I wasn鈥檛 being clear. I鈥檓 referring to an out-of-band conversation with other Yarn team members indicating they don鈥檛 think it鈥檚 very likely they鈥檇 be overwriting the installed package.json 馃槥
Edit: since this comment is now circulating on the web I want to clarify I didn鈥檛 bring it up with the Yarn team. I鈥檓 referring to an off-the-cuff remark by a single person on a technical aspect of this. That was not a decision but a casual three-word exchange between two people who sit in front of each other in the same room. I filed this issue for myself to look into it in case that it doesn鈥檛 get solved after I bring it up with the team properly (which I didn鈥檛 have time to do yet). I don鈥檛 know opinions of other team members and their manager, and don鈥檛 claim to represent them. There was most definitely no decision or even a discussion on this. I regret that my comment triggered a chain of misinformation.
oh. Well that sucks. Thanks for trying and taking the initiative to get this ball rolling anyway. lmk if there's anything else I can do to help.
There appears to be some movement on the Yarn issue/PR. Since solving it on our side would be very hacky in either case, I'm going to optimistically assume this gets solved there, and close this issue.
Most helpful comment
oh. Well that sucks. Thanks for trying and taking the initiative to get this ball rolling anyway. lmk if there's anything else I can do to help.