This repository has been archived by the owner on Jan 26, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 492
VS Code - debugging tests - cannot connect to runtime process, timeout after 10000 ms #209
Comments
The configuration you mentioned does no longer work in VS Code 1.19 and above, and regarding the issues listed in the VS Code repo, it only worked before due to a bug. See the comment from @weinand: The updated config should look like this (adopted):
A quick check with VS Code 1.19 on Win 10 with a freshly generated app confirmed that this works fine. References: |
When I last tried debugging in vs code + chrome it catched breakpoints only after page refresh. The same was about original CRA as well. |
jergason
pushed a commit
to jergason/create-react-app-typescript
that referenced
this issue
Mar 27, 2018
* Remove PropTypes from production build (wmonk#209) * Added react/forbid-foreign-prop-types rule to eslint config * Removed react/forbid-foreign-prop-types rule from eslint config
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
Yes
Which terms did you search for in User Guide?
react-scripts-ts vs code debug
react-scripts-ts vs code debug tests
typescript jest vs code Cannot connect to runtime process, timeout after 10000 ms
vs code Cannot connect to runtime process, timeout after 10000 ms
...
Environment
node -v
: 8.9.1npm -v
: 5.5.1yarn --version
(if you use Yarn):npm ls react-scripts-ts
(if you haven’t ejected): 2.8.0Then, specify:
Steps to Reproduce
Expected Behavior
It should start the debugging of tests.
Actual Behavior
Until a few seconds it shows error message:
![image](https://user-images.githubusercontent.com/20944757/34055695-ba9fbe00-e1d0-11e7-9244-da8f288b40aa.png)
The text was updated successfully, but these errors were encountered: