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
Currently the project contains both package-lock.json and yarn.lock. Unsurprisingly, this causes yarn to warn:
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
Is it intended for npm to be used, or for yarn to be used?
The text was updated successfully, but these errors were encountered:
Considering yarn and npm can be used with any package you please by killing the lock file you don't want and updating with your package manager of choice, I am not sure this has to be one or the other. I am open to suggestions, but I am not sure where attending to this question is going to land on the priority queue.
Currently the project contains both package-lock.json and yarn.lock. Unsurprisingly, this causes yarn to warn:
Is it intended for npm to be used, or for yarn to be used?
The text was updated successfully, but these errors were encountered: