Cannot find name 'MessageEvent'

I changed the value for lib in my “tsconfig.json” from ["dom", "es2017"] to ["es2017"] because I am working on a Node.js-only project (no Browser environment). Unfortunately, this broke my integration with “reconnecting-websocket”. I am getting now the following errors:

##[error]node_modules/reconnecting-websocket/dist/events.d.ts(20,14): error TS2304: Cannot find name 'MessageEvent'.
##[error]node_modules/reconnecting-websocket/dist/events.d.ts(30,22): error TS2304: Cannot find name 'MessageEvent'.
##[error]node_modules/reconnecting-websocket/dist/events.d.ts(31,30): error TS2304: Cannot find name 'MessageEvent'.
##[error]node_modules/reconnecting-websocket/dist/reconnecting-websocket.d.ts(24,54): error TS2304: Cannot find name 'Blob'.
##[error]node_modules/reconnecting-websocket/dist/reconnecting-websocket.d.ts(54,17): error TS2304: Cannot find name 'BinaryType'.
##[error]node_modules/reconnecting-websocket/dist/reconnecting-websocket.d.ts(96,25): error TS2304: Cannot find name 'MessageEvent'.

When digging into “reconnecting-websocket.ts”, I realized that it expects “MessageEvent” to come from TypeScript’s internal “DOM” library which is not available in a Node.js environment.

On Node.js the MessageEvent can be retrieved from the “ws” package:

import WebSocket, {MessageEvent} from 'ws';

Can this information be included in “reconnecting-websocket”?

[HouCoder]

Thanks @bennyn for your quick response.

[bennycode]

Ideally, “reconnecting-websocket” would use “@types/ws” which has a definition for WebSocket.MessageEvent:

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/47e9cf6d8947e46a82bb09bbcc3dd74a3ac0ffa1/types/ws/index.d.ts#L188-L192

Unfortunately, “reconnecting-websocket” currently relies on the “dom” lib that ships with TypeScript. That’s why you would have to write your own definition for MessageEvent if you like to use it with React Native.

Example:

declare global {
  interface MessageEvent {
    data: string;
    type: string;
  }
}