Matt Mazzola

Hmm, based on the issue you linked it seems to match the CRA docs I referenced. Assuming we have the same launch configuration and yours works and mine doesn't maybe...

> The launch configuration does not even mention the inspect resp. inspect-brk argument This part is specificed as: `"protocol": "inspector",` and then from my understanding VS Code looks at the...

Also, the manual `test:debug` script they recommend (I linked in original post) manaully specifies `inspect-brk` and this still doesn't work. `"test:debug": "react-scripts-ts --inspect-brk test --runInBand --env=jsdom",`  Do you have...

Well I'm at least a step closer, but still not able to hit breakpoints. I updated VSCode to `1.21` and react-scripts-ts to `2.13.0` to match and the launch command now...

Ah yea, I meant the other versions, not node. I'm still at loss. Here's what I tried for minimal reproduction of issue: Updated to node 8.10.0 1. Create app ```...

Yea, this bug has confused me too. I think the position of the command line options should not matter. npm and bower behave this way so if developers grow habit...

I can understand the reason for using window.opener, but I'm not following how you can do it without async. The act of user filling out the login form seems inherently...

Related to this issue, I would want to know, **what the best way to debug this type of issue?** I have turned on Debug logging on both of the DAPR...

> Can you just use our official dev container here? https://github.com/dapr/dapr/blob/master/.devcontainer/devcontainer.json > That should docker in docker -- which is probably what isn't working for you right now. I agree...

I wasn't sure which part you wanted to look at. I think your link on shows a snippet or single file of the "hello-world-compose" sample. In my first post I...