AbortSignal conflict issue between @types/web@0.0.70 and @types/node@18.6.1

[cjones26]

With the latest release of @types/web@0.0.70 being installed side-by-side with @types/node@18.6.1, we are receiving the following conflict:

../../node_modules/@types/node/globals.d.ts:72:13 - error TS2403: Subsequent variable declarations must have the same type.  Variable 'AbortSignal' must be of type '{ new (): AbortSignal; prototype: AbortSignal; timeout(milliseconds: number): AbortSignal; }', but here has type '{ new (): AbortSignal; prototype: AbortSignal; }'.

72 declare var AbortSignal: {
               ~~~~~~~~~~~

  ../../node_modules/@typescript/lib-dom/index.d.ts:1982:13
    1982 declare var AbortSignal: {
                     ~~~~~~~~~~~
    'AbortSignal' was also declared here.


Found 1 error in ../../node_modules/@types/node/globals.d.ts:72

Any suggestions would be greatly appreciated, though we've pinned @types/web@0.0.69 for now.

[ornicar]

Just a note, the current version is 0.0.70 and the last working version is 0.0.69. (Not 0.70 and 0.69)

[cjones26]

Just a note, the current version is 0.0.70 and the last working version is 0.0.69. (Not 0.70 and 0.69)

Thanks, I've updated my post.

[mathe42]

See also DefinitelyTyped/DefinitelyTyped#60868 and DefinitelyTyped/DefinitelyTyped#61412

[saschanaz]

#1365 added AbortSignal.timeout and that seems the cause of the conflict. #1093 worked around this last time by removing AbortSignal.abort, but not sure we should do the same here.

I'd prefer waiting #60868.

[fernandopasik]

Is there any workaround besides pinning @types/web@0.0.69?