Possible Race Condition when catching native events

[justin0mcateer]

We are using a networking library (libp2p) which has a transitive dependency on pEvent. We have identified a race condition where pEvent misses the 'open' event emitted by a DataChannel. The code in pEvent appears to synchronously build up a set of Promises to implement it's functionality, so it appears this race condition would not be possible. However, I wonder if because the 'open' event is being emitted by native code, the event can in fact be raised while pEvent is setting up its event handler.

We have a reproducible problem, with a functioning workaround, so we have a pretty high level of confidence that this is what is happening. I don't have anyway to verify, but it seems that this issue could also occur with any other 'native' events, such as DOM events, etc.

The details on the issue are captured in this issue on the downstream library:
libp2p/js-libp2p#2443

[sindresorhus]

There's really nothing this package can (or should) do if the native add-on does not adhere to JavaScript semantics (single-threadedness).