Closed TheKnarf closed 4 years ago
The first error about sodium bindings is, as far as I know, just a warning. It tries to use the native compiled version of libsodium, but if it cannot find it it'll fall back to a javascript version. You can get rid of the warning by invoking npm install -g sodium-native
.
I also suffer from the second error, and don't know how to solve that yet.
I think the second issue is the same as described here: https://github.com/ssbc/patchwork/issues/610#issuecomment-388647395
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?