Missing TypeScript types in version 0.13.x (no typings exported)

[lekting]

Hi!
After updating from binance-api-node@0.12.9 to 0.13.x, the library no longer provides any TypeScript definitions.

In the previous version (0.12.9), the package included TypeScript typings (e.g., BidDepth, Depth, NewFuturesOrder, NewOrderMarketBase, etc.), and everything worked correctly.

However, in 0.13.x:

There is no types/ directory

No .d.ts files are included in the published npm package

TypeScript cannot find or import any types from the library

Even the main module has no exported typings at all

This makes the TypeScript integration effectively broken.

Thanks!

[carlosmiei]

@lekting Hello, thanks for reporting it, that's not expected we will check it and get back to you.

[carlosmiei]

@lekting I have checked and the types file is included in the base directory and the package.json points to that file

@lekting is it possible to provide a small POC project showcasing the issue?

[carlosmiei]

@lekting OK I think this commit might have caused the issue: 5f48fde

Looking into it

[carlosmiei]

@lekting I'm explicitly exposing all types here #686 to make them more accessible, but please take into consideration that the lib was upgraded and some of the types changes, since it follows a different struct now and most endpoints use an inline object type instead of a type.

Eg: futuresCandle return type now is

  futuresCandles(payload: { symbol: string; interval: string; startTime?: number; endTime?: number; limit?: number }): Promise<Array<{
    openTime: number;
    open: string;
    high: string;
    low: string;
    close: string;
    volume: string;
    closeTime: number;
    quoteVolume: string;
    trades: number;
    baseAssetVolume: string;
    quoteAssetVolume: string;
  }>>;

instead of Promise<CandleChartResult[]>

[lekting]

Thanks, @carlosmiei!
Appreciate the quick investigation and detailed explanation 🙏

The clarification about the updated structure and inline types makes sense. I’ll adjust my implementation accordingly and test everything once #686 is merged.
Thanks again for the fast response and for exposing the types explicitly — that definitely helps!

[carlosmiei]

@lekting We have released a new version (0.13.3) that exposes all types explicitly, but please take into consideration what I explained above.

Nonetheless, we will consider going back to proper types; it is the best approach to typing.

Thanks for bringing our attention to this and let us know if anything.

[lekting]

@carlosmiei i've tested in my project, but its doesn't work properly. I've created project on github where you can test it.

new types, that you exported - exists only as "export" variable in index.d.ts file, but /types folder isn't exists from that exports and throwing an error.

[carlosmiei]

@lekting I will check it again thanks for the feedback

[carlosmiei]

@lekting can you please upgrade and try again? I released 0.13.4 and it should be working as expected now