This implementation was assuming the use of the legacy node-abort-controller package instead of the global AbortController. The legacy package supports dispatching strings as events, but the AbortSignal as implemented in the Node.js API from 15.x forward only accepts Event objects.
This also explicitly drops support for Node.js 14. elasticsearch-js dropped it a while ago, but it didn't need to get dropped on the transport until now.
This implementation was assuming the use of the legacy node-abort-controller package instead of the global
AbortController. The legacy package supports dispatching strings as events, but theAbortSignalas implemented in the Node.js API from 15.x forward only acceptsEventobjects.This also explicitly drops support for Node.js 14. elasticsearch-js dropped it a while ago, but it didn't need to get dropped on the transport until now.
See https://github.com/elastic/elastic-transport-js/issues/73.