fix(errors): export error helpers and types from package entry point

[Tyagiquamar]

Fixes #1848

Summary

\�rrors.ts\ defines key error helpers, types, and error code mappings (\isAPIError, \isErrorRetryable, \APIErrorCodes, \isConnectionIDError, \isWSFailure, \isErrorResponse, \APIError), but they were not exported from the package entry point (\src/index.ts).

Changes

• Added \�xport * from './errors';\ to \src/index.ts\ so SDK consumers can import error classification utilities directly from \stream-chat.

[szuperaz]

Thanks for the PR, exporting error helpers makes sense. However adding tests that assert something is exported from the client is not something we do, can you please revert the new test?

[Tyagiquamar]

Reverted the export assertions test as requested. The PR now only includes the error helper/type exports in src/index.ts.

[MartinCupela]

@Tyagiquamar what is that you are missing from the errors.ts file? I believe the contents were not exported on purpose.

[Tyagiquamar]

The main missing pieces are isAPIError, isErrorRetryable, and APIErrorCodes, as described in #1848.

The use case is an app-level retry policy: consumers can fail fast on non-retryable API errors and retry things like rate limits/timeouts using the retryability information the SDK already maintains.

Currently these helpers exist in errors.ts, but they aren't importable from the stream-chat package entry point. If exporting the whole module isn't intended, I'm happy to narrow this to only the helpers/types you consider part of the public API.

[szuperaz]

Looks good to me now, lets also wait for @MartinCupela's review

[MartinCupela]

It looks like the list of APIErrorCodes is incomplete. I will create a new PR that fixes it.

[Tyagiquamar]

It looks like the list of APIErrorCodes is incomplete. I will create a new PR that fixes it.

Thanks, that makes sense. I'll leave this open for now so we can revisit the public exports once your APIErrorCodes update lands. If you'd prefer this PR to be closed in favor of your change, I'm happy to do that.

[MartinCupela]

I have asked for a review by the BE team. The issue is that such a list can get our of sync pretty fast, so there is discussion, whether we could do better. If not, I will provide reviewed updated list and export it.