Aziz Khoury

this is just a client to the Mandrill API, the documentation of all requests are here: https://mandrillapp.com/api/docs/ as for the html part see this https://github.com/jimrubenstein/node-mandrill/issues/11

we could use file locking i guess, maybe try https://github.com/moxystudio/node-proper-lockfile

can you link the question please?

well, what if it's a different process writing to the same file?

honestly it looks like you haven't installed it? ``` npm install node-persist ``` or ``` yarn add node-persist ``` or maybe you've done `npm install` but it's not in your...

so let get this straight, when you do this, this causes an error ``` const storage = require('../node_modules/node-persist'); ``` but this doesn't? ``` const storage = require('node-persist'); ```

because your code includes both, the first one being commented out ``` //const storage = require('../node_modules/node-persist'); const storage = require('node-persist'); ```

hmm, sorry I am not sure I can help without a test case where I can reproduce it.

ok you can use `forgiveParseErrors: true` in the init options to ignore unrecognized files and directories in your storage dir >>> in some cases, you (or some other service) might...

`setItem` already returns a promise, why can you use that? wait for each promise to resolve then call the next one. Or you can use `setItemSync()`, no wait, you wanted...