Describe the bug
After compiling snow, if I try to run snow init (while in a newly created directory), node spits out

node:events:342
      throw er; // Unhandled 'error' event
      ^

Error: spawn lsof ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn lsof',
  path: 'lsof',
  spawnargs: [ '-X', '-F', 'pcan', ' D', 'hey' ]
}

The .snow folder is still created, however if I try to run snow add . (and a few other snow commands), I get the error

No HEAD found
fatal: no reference nor HEAD found

In .snow/log/mainlog, there is 1 line: 1633564812686 -0700 $> init: initialized at /home/[filepath]/test_snow, so the repo seems to have initialized successfully, but all other (non-log) folders in .snow are empty.

To Reproduce
Steps to reproduce the behavior:
[be using zsh/linux/ext4]

1. Compile snow via the instructions on the README
2. Create a folder, switch to it, and snow init
   ^ this will cause a node error
3. copy a file into the current folder and execute snow add .
   ^ this will raise a "no HEAD found" error

Expected behavior
snow init shouldn't throw any errors, and snow add . shouldn't fail

Desktop (please complete the following information):

• OS: Arch Linux (x86 with Node.js installed)

Additional context
I'm a node newbie so maybe I made some sort of obvious mistake ... if I did, I'm sorry for wasting your time