Skip to content

AbortSignal conflict issue between @types/[email protected] and @types/[email protected] #1368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cjones26 opened this issue Jul 26, 2022 · 5 comments

Comments

@cjones26
Copy link

cjones26 commented Jul 26, 2022

With the latest release of @types/[email protected] being installed side-by-side with @types/[email protected], 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/[email protected] for now.

@ornicar
Copy link

ornicar commented Jul 27, 2022

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 cjones26 changed the title AbortSignal conflict issue between @types/[email protected] and @types/[email protected] AbortSignal conflict issue between @types/[email protected] and @types/[email protected] Jul 27, 2022
@cjones26
Copy link
Author

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
Copy link
Contributor

mathe42 commented Aug 14, 2022

@saschanaz
Copy link
Contributor

#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
Copy link

Is there any workaround besides pinning @types/[email protected]?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants