Hi Lacy,
the figure df shows is misleading since we use compression to squeeze out the most from those 128MB we provide to each project. When you start reaching your quota, weird things start happening, as you can see. To get better figures, you can try to run sync so that changes are flushed to the filesystem.
As for the missing dependencies, I am not 100% sure, it might be some mistake npm is doing on their end, due to not enough space. I’ll dive into it further.
The reason why you’re running out of space is that you’re storing the image in a directory tracked by git: this means that even if you replace the image every time a new one arrives, the images are stored into the git history (we commit changes automatically every few minutes)! To free some space, you can rm -rf .git if you don’t care about your git history so far (this doesn’t affect exports nor backups), and then add a .gitignore file with the following content:
public/latest.jpg
Thanks for reporting and happy coding 