t.rejects is documented to return a promise, but returns undefined instead

[timmolendijk]

About the rejects assert, the documentation claims:

it returns a Promise that resolves when it is completed

Source: https://github.com/tapjs/node-tap/blob/gh-pages/asserts/index.md#trejectspromise--fn-expectederror-message-extra

This seems not to be the case:

const tap = require('tap');

tap.test("where is my promise", async t => {
  t.type(t.rejects(Promise.reject(new Error())), Promise);
});

gives

TAP version 13
# Subtest: where is my promise
    ok 1 - expect rejected Promise # time=6.096ms {
        ok 1 - expect rejected Promise
        1..1
    }

    not ok 2 - type is Promise
      ---
      found: undefined
      wanted: Promise
      compare: ===
      at: {}
      ...

    1..2
    # failed 1 of 2 tests
not ok 1 - where is my promise # time=18.532ms

1..1
# failed 1 test
# time=26.419ms

---

I'm running node-tap v10.7.2 on Node v8.6.0

[isaacs]

Fixed in v11. Thanks!