https://github.com/louis-bompart/automatic-dollop
Minimum Reproducible Example for conPty issue with node-pty@0.10.0
https://github.com/louis-bompart/automatic-dollop
node pty windows
Last synced: 6 months ago
JSON representation
Minimum Reproducible Example for conPty issue with node-pty@0.10.0
- Host: GitHub
- URL: https://github.com/louis-bompart/automatic-dollop
- Owner: louis-bompart
- Created: 2021-04-26T22:00:11.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-04-26T22:41:10.000Z (over 4 years ago)
- Last Synced: 2025-02-15T11:45:18.229Z (8 months ago)
- Topics: node, pty, windows
- Language: TypeScript
- Homepage:
- Size: 2.93 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# node-pty-test
Minimum Reproducible Example for an issue with [conPty](https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/) in [microsoft/node-pty](https://github.com/microsoft/node-pty) v0.10.0.
## Environment:
- OS: Tested on Windows 10.0.19041
- Node: nvm w/ 14.16.0
- Command Interpreters:
- Powershell 5.1.19041.906
- Powershell 7.1.3
- Cmd 10.0.19041.928
## How to reproduce:
- `npm run start-conpty`: Should 'flush' the command interpreter and just hang
- Using `wmic process get processid,parentprocessid,executablepath` you can see that `conhost.exe` is still running w/ `node.exe` as its parent process.
- `npm run start-winpty`:
- Should not flush the command interpreter and just display the message
- The command interpreter input should be freed and all the process of the test should be closed.
## Expected behaviours:
- `npm run start-winpty` behaviour should not change
- `npm run start-conpty` behaviour should match the one of `npm run start-winpty`