Closed lhvy closed 1 year ago
Huh - that's probably my fault. I often use npm install
rather than yarn install
- just deleted the package-lock.json and add it to the .gitignore in case I fuck that up again.
Sounds good! I'll let this issue close with linked PR.
Currently the codebase has both
package-lock.json
andyarn.lock
, and runningyarn install
gives the following error:I believe, we should decide if we are using Yarn or not, and remove the other file.