Skip to content
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

AbortSignal error caught while running the server from glee cli #708

Closed
afzal442 opened this issue Jul 31, 2023 · 8 comments
Closed

AbortSignal error caught while running the server from glee cli #708

afzal442 opened this issue Jul 31, 2023 · 8 comments
Labels
bug Something isn't working

Comments

@afzal442
Copy link

Describe the bug

A clear and concise description of what the bug is.

> [email protected] dev
> glee dev

 TS Compiling TypeScript sources...
 TS 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; abort(reason?: any): AbortSignal; timeout(milliseconds: number): AbortSignal; }', but here has type '{ new (): AbortSignal; prototype: AbortSignal; }'.

How to Reproduce

Steps to reproduce the issue. Attach all resources that can help us understand the issue:

Run asyncapi new glee
Get to the project dir
Run npm run dev after npm i

@KhudaDad414 @Souvikns

@afzal442 afzal442 added the bug Something isn't working label Jul 31, 2023
@afzal442
Copy link
Author

afzal442 commented Aug 2, 2023

Hi maintainers, can I get a signal here if I this is relevant? if any error occurs?

@Souvikns
Copy link
Member

Souvikns commented Aug 3, 2023

Yeah, I am getting the same error, for some reason when I install @types/node it runs can you manually create a project and see if you are getting the same error?

@KhudaDad414
Copy link
Member

@afzal442 @Souvikns I can't reproduce this:
Screenshot 2023-08-29 at 10 07 22
I am using node 18 on Mac

@afzal442
Copy link
Author

Let's e-meet sometime. 😄

@peter-rr
Copy link
Member

peter-rr commented Sep 8, 2023

@afzal442
I cannot reproduce the error either:

Monosnap 266617494-97b058fd-7066-46fc-91b2-940ed01a86bd png (621×240) 2023-09-08 15-02-34

I guess the issue has already been solved with this fix, related to what @Souvikns commented above.

@Souvikns
Copy link
Member

Souvikns commented Sep 8, 2023

Yeah, we can close this, It has been fixed with this #783.

@afzal442, update your CLI and it should work now.

@afzal442
Copy link
Author

afzal442 commented Sep 8, 2023

That's cool. I checked it yesterday. Let me do it again

@afzal442
Copy link
Author

afzal442 commented Sep 8, 2023

It's working fine as on asyncapi 0.54.7

@afzal442 afzal442 closed this as completed Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants