You seemed to have found a bug. (I get the same error if I pass “” or null for set.) Unfortunately, I am not aware of any workaround for this but I will definitely pass it along to our engineers and keep you posted.
Thanks for reporting this.
Currently there’s a bug in the API which doesn’t seem to handle to case, you have mentioned.
However if the key structure is as follows
key = { ns: ns_name, key: key_value}
Then write works fine.
We will soon fix the case you have mentioned and release it to npm repository.
Thanks again for your patience.