Abort signals and node compatibility

Deno and Node's AbortSignalAbortSignal types are not compatible. I have verified that I can use a deno AbortSignal with the node:eventsnode:events APIs (at least EventEmitter.once()EventEmitter.once(), but I have to cast them to Node's own type if I want to get rid of errors:

export { EventEmitter } from 'node:events'
export type { AbortSignal as NodeAbortSignal } from 'npm:@types/node'

// …then cast any signal to `signal as NodeAbortSignal`.

export { EventEmitter } from 'node:events'
export type { AbortSignal as NodeAbortSignal } from 'npm:@types/node'

// …then cast any signal to `signal as NodeAbortSignal`.

Without the cast, I get the error below.

Is there a better/cleaner way?
Thanks.

Deno•3y ago•

3 replies

jcayzac

Abort signals and node compatibility

export { EventEmitter } from 'node:events'
export type { AbortSignal as NodeAbortSignal } from 'npm:@types/node'

// …then cast any signal to `signal as NodeAbortSignal`.

export { EventEmitter } from 'node:events'
export type { AbortSignal as NodeAbortSignal } from 'npm:@types/node'

// …then cast any signal to `signal as NodeAbortSignal`.

Without the cast, I get the error below.

Is there a better/cleaner way?
Thanks.

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Deno

Chat about Deno, a modern runtime for JavaScript and TypeScript.

20,934 Members

Join

Abort signals and node compatibility

Abort signals and node compatibility

Continue the conversation

Deno

Continue the conversation

Deno

Similar Threads