-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MaxListenersExceededWarning in Windows #887
Comments
@SBoudrias I've diagnosed this issue while trying to fix it in Amplify CLI where we're leveraging Inquirer to drive the console prompts. |
@SBoudrias is it possible that this bug is caused by #882 (03412e5)? It appears that change makes it so that the readline interface does not get closed on windows. |
@rizzlesauce that's possible; but closing the readline on windows was making the prompt unresponsive. The best solution on the longer term is probably moving away from rxjs altogether. I've made a lot of progress on this #692 - but I'm running out of time to complete a release. I'm okay to review a PR if anyone wants to take the time. |
this is happening in 7.3.3 of inquierer going to have to move off this package for this reason |
@nanomosfet take a look at the |
I am getting memory leaks on 8.2.4 on trace it seems like |
Yeah, |
Hi, Can I have a direct link? |
Over here: https://www.npmjs.com/search?q=%40inquirer |
This is also happening on Linux, but it has been fine until recently so I am not entirely sure what happened. |
Closing this ticket as stale. Open new issues if you encounter problems with the new Inquirer API. |
I run packages/inquirer/examples/recursive.js.
In 7.0.4 (latest) on Windows, I get a MaxListenersExceededWarning:
The MaxListenersExceededWarning occurs in 7.0.4 and 7.0.2
It does not occur in 7.0.3 and <=7.0.1.
My environment is
The text was updated successfully, but these errors were encountered: