Thanks for the nifty package!

I noticed in the README you describe it as a "blocking" sleep, but as far as I can tell, that isn't the case? It's kind of a nit-pick, but when it comes to sleeping in Node APIs it's a pretty important distinction. This will certainly block the function where it's used from continuing until the promise resolves, but the event loop will continue handling other requests. Here's a demo:

Non-blocking sleep

const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));

async function sleepThenLog() {
  await sleep(5000);
  console.log('slept for 5000ms');
}

async function immediatelyLog() {
  console.log('no sleep at all');
}

sleepThenLog();
immediatelyLog();

Returns:

no sleep at all
...5000ms delay
slept for 5000ms

Blocking sleep (requires node 9.3+)

async function sleepThenLog() {
  Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 5000)
  console.log('slept for 5000ms');
}

async function immediatelyLog() {
  console.log('no sleep at all');
}

sleepThenLog();
immediatelyLog();

Returns (after 5000ms):

slept for 5000ms
no sleep at all

As in topic, package description mislead. Imo. this function is non-blocking:
https://github.com/sqren/await-sleep/blob/3b4ba9421df46b081e770bf832320c1bbcf33e0e/package.json#L4

I'm currently using this and when I deploy to AWS it gives me this response. Currently working in an asynchronous typescript environment.

TypeError: await_sleep_1.default is not a function at Object.<anonymous> (/var/task/src/service/Customer.js:41:36) at next (native) at fulfilled (/var/task/src/service/Customer.js:4:58) at process._tickDomainCallback (internal/process/next_tick.js:135:7) }

It's imported like so import sleep from 'await-sleep' and put in my service function like so await sleep(1500);

thanks!