We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Either for all modules as a global option, or one a module-by-module basis as part of their config in lookup.json.
lookup.json
Using something like https://github.com/chjj/pty.js
This is to help stop issues like nodejs/node#8138 before they're released.
The text was updated successfully, but these errors were encountered:
I believe @bcoe was looking into this. Did you have nay progress?
Sorry, something went wrong.
@thealphanerd as far as yargs is concerned, yargs/yargs#597 should take care of it. Having pty support in citgm might be still nice to have, though.
Having some sort of instruction to use pty.js instead of the regular stdio options when spawning a new process is probably all that is needed here?
Unfortunately I think most people don't even know about that sort of difference.
Successfully merging a pull request may close this issue.
Either for all modules as a global option, or one a module-by-module basis as part of their config in
lookup.json
.Using something like https://github.com/chjj/pty.js
This is to help stop issues like nodejs/node#8138 before they're released.
The text was updated successfully, but these errors were encountered: