Describe the bug
I noticed we have both package-lock.json and yarn.lock files in the repo. We should pick one and stick to it. Typically I use yarn, but I'm happy to go with whatever works. Any preference?
To Reproduce
Steps to reproduce the behavior:
peep the repo
Expected behavior
We should only have one lockfile. The resolution of this issue should remove one or the other, and add that one (the removed one) to .gitignore. This should be mirrored in /functions/ as well, where a different list of dependencies is maintained.
Describe the bug I noticed we have both package-lock.json and yarn.lock files in the repo. We should pick one and stick to it. Typically I use yarn, but I'm happy to go with whatever works. Any preference?
To Reproduce Steps to reproduce the behavior:
Expected behavior We should only have one lockfile. The resolution of this issue should remove one or the other, and add that one (the removed one) to
.gitignore
. This should be mirrored in/functions/
as well, where a different list of dependencies is maintained.Actual Behavior n/a really, but as far as I know it's not ideal to have both 🤔
Screenshots![image](https://user-images.githubusercontent.com/1844496/91670689-b13dfd80-eaed-11ea-9ece-381db7757ee6.png)