WebSocket is not defined (Node + Webpack) about stompjs HOT 8 CLOSED

Thanks for the workaround. While this itself may not be a bug, the code should not refer to WebSocket as WebSocket is technically not needed to use this library.

from stompjs.

@kum-deepak very welcome ! I was surprised to see that the object was referenced globally. Why not use a reference to this._wesocket which seems to be referenced from the code in many places ?

from stompjs.

Fixed and released in 5.4.2.

from stompjs.

still exists v5.4.2

from stompjs.

Please share details about your setup and copy of console log.

from stompjs.

stompClient = function () {
const stompConfig = {
connectHeaders: {
login: "##########",
passcode: "############"
},
brokerURL: "#########",
reconnectDelay: 10000
debug: function (str) {
logger.trace([AMQ-PRODUCER] TRACE - ${str});
},
beforeConnect: function () {
logger.info([AMQ-PRODUCER] START CONNECT);
current_state = STATE.WAIT;
},
onConnect: function () {
logger.info([AMQ-PRODUCER] CONNECTED);
current_state = STATE.CONNECTED;
},
onDisconnect: function () {
logger.info([AMQ-PRODUCER] DISCONNECTED);
current_state = STATE.DISCONNECTED;
},
onStompError: function (err) {
logger.error([AMQ-PRODUCER] ERROR: ${JSON.stringify(err)});
current_state = STATE.ERROR;
this.forceDisconnect();
}
};
return new Stomp.Client(stompConfig);
};

const client = stompClient();
client.activate();

(node:14436) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:14436) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:14436) UnhandledPromiseRejectionWarning: ReferenceError: WebSocket is not defined
at Client../src/client.ts.Client._createWebSocket (C:\Users\m.shaaban\Cequens\Projects\sms_http_bulk_interface\node_modules@stomp\stompjs\bundles\stomp.umd.js:419:13)
at Client. (C:\Users\m.shaaban\Cequens\Projects\sms_http_bulk_interface\node_modules@stomp\stompjs\bundles\stomp.umd.js:359:48)
at step (C:\Users\m.shaaban\Cequens\Projects\sms_http_bulk_interface\node_modules@stomp\stompjs\bundles\stomp.umd.js:165:23)
at Object.next (C:\Users\m.shaaban\Cequens\Projects\sms_http_bulk_interface\node_modules@stomp\stompjs\bundles\stomp.umd.js:146:53)
at fulfilled (C:\Users\m.shaaban\Cequens\Projects\sms_http_bulk_interface\node_modules@stomp\stompjs\bundles\stomp.umd.js:137:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
(node:14436) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

from stompjs.

Please check https://stomp-js.github.io/faqs/2019/05/20/faqs.html#p-can-this-library-be-used-with-nodejs-p

If that does not help, please share your Stomp Config.

from stompjs.

i'm already solve this problem by using this workaround
Object.assign(global, {
WebSocket: websocket.w3cwebsocket,
// Not needed in node 11
TextEncoder: TextEncodingPolyfill.TextEncoder,
TextDecoder: TextEncodingPolyfill.TextDecoder
});

but when i'm seeing your commit 'Fixed and released in 5.4.2.'
i think that i can use it without this workaround

from stompjs.