When using in on another server that uses mysql-async there are problems. Everything is fine with mysql-async until Hypnonema makes a call to its own .db file and then after that mysql-async begins erroring on their return function (@mysql-async/mysql-async.js:15543) and all returns from mysql-async from that point are null. Is there a possibility of making this safe for mysql-async such as allowing for use of mysql-async instead of the liteDB one or perhaps even just a local json option. I only have 2 screens I need to keep up with.
When using in on another server that uses mysql-async there are problems. Everything is fine with mysql-async until Hypnonema makes a call to its own .db file and then after that mysql-async begins erroring on their return function (@mysql-async/mysql-async.js:15543) and all returns from mysql-async from that point are null. Is there a possibility of making this safe for mysql-async such as allowing for use of mysql-async instead of the liteDB one or perhaps even just a local json option. I only have 2 screens I need to keep up with.