Thank you for calling this out. It's a good suggestion for us to extend AirtableError from Error. We will look into this and see if we can introduce this without breaking backwards compatibility.

This would be a very nice addition. It's a bit difficult to debug failures at the moment since you have add your own logging to identify where errors are occurring.

Hi folks, our team lost some time in our new project since we we couldn't figure out where this error was coming from without a stack trace. Just want to add a vote to the suggestion of extending the Error object in this and how simple/valuable that would be to get our exception handler (sentry in this case) to actually surface the stacktrace.

I've raised a PR that fixes this: #402.

This makes errors significantly easier to debug and trace down! Although note that this doesn't make the errors perfect - by the way the SDK is constructed errors that are raised in asynchronous contexts still sometimes don't have the most useful stacktraces.