-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Jest hangs when quitting watch mode if dev tools are still attached #5028
Comments
andyearnshaw
added a commit
to andyearnshaw/jest
that referenced
this issue
Dec 6, 2017
andyearnshaw
added a commit
to andyearnshaw/jest
that referenced
this issue
Feb 13, 2018
andyearnshaw
pushed a commit
to andyearnshaw/jest
that referenced
this issue
Feb 13, 2018
jessecarfb
pushed a commit
to jessecarfb/jest
that referenced
this issue
Feb 14, 2018
* Revert setRawMode on --watch ctrl-c (jestjs#5028) * Disable stdin raw mode in watch quit plugin (jestjs#5028) * Update changelog
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Jest won't close until the dev tools are closed when run with the
--watch
parameter, Ctrl-C and Ctrl-\ are ignored.If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can
yarn install
andyarn test
.npx -n --inspect jest --watch
.What is the expected behavior?
Ctrl-C or Ctrl-\ should quit the process, allowing the dev tools to remain open to connect to the next available node process. When the
--watch
parameter is not provided, jest works as expected.Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
Jest: v21.2.1
Node: v8.9.2
NPM: 5.5.1
OS: macOS High Sierra
The text was updated successfully, but these errors were encountered: