Deepak Kumar

Fixed in https://github.com/stomp-js/stompjs/commit/a6cfd415735323f56229e434554144bd4a659043

Please enable debug and attach the full console output.

A long discussion on seemingly a simple issue. The underlying STOMP connection is not guaranteed to be always there - it may vanish at any time. The reconnection logic will...

Consider for v7.

The next version is compiled with `strictNullChecks` set. See commit https://github.com/stomp-js/stompjs/commit/06ff8fca4199ec3669ef795e85284b9fcdcf1326.

The current version is released as `es2015` (https://github.com/stomp-js/stompjs/blob/develop/tsconfig.json#L5). Please verify that you are using the latest version before I dig deeper.

I tried your project. What I can figure out: - The code compiles correctly with `tsc` (which your report suggests as well). - When used with `nodemon` which internally uses...

For reference the `tsconfig` that works: ``` { "compilerOptions": { "esModuleInterop": true, "module": "UMD", "target": "es2022", "moduleResolution": "node", "outDir": "dist", "strict": true }, "include": [ "./src/**/*" ], "ts-node": { "esm":...

In such cases in the past, I used the library in the source code form - by using the original .ts files and compiling these along with my project code....

This package is distributed as UMD and ESM. NodeJS does not honor the module key in package.json. Ref https://nodejs.org/api/packages.html#packages_exports and https://nodejs.org/api/packages.html#dual-commonjses-module-packages