Can the new error types be exported?

[ziltodian]

Hi @oleiade ,

WRT this, thanks for adding the additional error types. However, we're still unable to check for an instance of the new errors as they're not exported. Would it be possible for the new errors to be exported so we can check for an instance of NetworkError?

Thanks

[oleiade]

Hey @ziltodian 👋🏻

For sure, we haven't managed to publish a new release yet, but we'll try to get that done as soon as possible. Errors will be exported both from the main index.js file, as well as client-specific ones 🙇🏻

[oleiade]

Hi @ziltodian 👋🏻

We have published a new release of jslib-aws (v0.13.0). Error types are now exported from every bundles. Could you give it a spin, and let us know if that addresses the issue for you? 🙇🏻

PS: in order to keep the issue backlog manageable, without answer, I will close this in one week 👍🏻

[ziltodian]

Hi @oleiade , I've actually made the change to use NetworkError today. It's currently in review. I'll keep you posted.

[ziltodian]

Hi @oleiade , we've been able to update our code to check for an instance of NetworkError. Many thanks for the changes. Some feedback I have is that it might also be helpful to re-export the NetworkErrorName type and the *ErrorKind enums.

[oleiade]

Hi @ziltodian 👋🏻

If you have the capacity to do so, I think that would be a good first issue to make a PR for.

Let me know if you don't and I'll find a moment to adress it myself 🙇🏻