Types issues and general node/typescript compatibility

[Rulikkk]

1. It looks like the .ws namespace in the client is present in runtime/javascript, however, it is completely missing in d.ts files. So, generally, websocket APIs are unusable from typescript, without dirty hacks.
2. package.json lacks type: "module" or any other definition
3. Also, it looks like many types exist in .d.ts files, and are essentially not usable in typescript source code (see sample below)

// assume following import
import { OrderSide } from "binance-api-node";

// then use it
const orderSide = OrderSide.BUY;

In this sample, when TS is compiled to JS, the OrderSide won't exist in JS context and import will fail, because initially OrderSide comes from .d.ts file, which does not get to compiled JS output.

[Rulikkk]

4. The futuresOrder func implicitly may create either plain order or algoOrder. In that case, binance API response is different in shape. However, this is not reflected in types: they follow only the plain order response shape

[carlosmiei]

@Rulikkk Thanks for reporting it, we will take a look

[carlosmiei]

@Rulikkk Can you please upgrade and try again? We have released a new version with the fix binance-api-node@0.13.7

[Rulikkk]

I am impressed, thank you! Will check and report.

[carlosmiei]

@Rulikkk Just let us know if anything! 🙏