Missmatch between undefined/null

In index.d.ts (around line 153) it is stated that findOne, findOneAndDelete, and findOneAndUpdate return a Promise of the collection type, or undefined.

But in fact all of these return null, not undefined when no document is found.

This is quite annoying when using TypeScript, since it will error with Object is possibly undefined if you do not check for this, but checking with !== undefined only calms typescript down. It does nothing at runtime. However, checking with != undefined, or checking if the object is truthy does work at both compiletime and runtime.

[mathieudutour]

Absolutely yes

[mathieudutour]

yep, totally ok 👍