if you already require('http') then you don't need typedef?

tried this also, didn't work for me, maybe it's the right way to do it...

what did work was:

class X {
  static CONNECTING = 1
  CONNECTING = 1
}

or like a mention earlier: x.CONNECTING = 1
but then it dose not have the right descriptor (unless you add those with defineProperties)

Does it work with

Object.defineProperty(WebSocket.prototype, 'CONNECTING', { enumerable: true, value: 0 });
Object.defineProperty(WebSocket, 'CONNECTING', { enumerable: true, value: 0 });

(without the loop)?

The same pattern is also used here https://github.com/websockets/ws/blob/7.5.2/lib/websocket.js#L402-L411. I'm not sure I want to change it. It is not a JSDoc issue. It is simply not documented/commented :)

without the loop it did work fine doing just

Object.defineProperty(WebSocket.prototype, 'CONNECTING', { enumerable: true, value: 0 });

tried it if it would work with a object using defineProperties

Object.defineProperties(WebSocket, {
  CONNECTING: {
    enumerable: true,
    value: 0
  }
});

The result: Property 'CONNECTING' does not exist on type 'typeof WebSocket'