chore(gatsby): Add yarn shortcuts for running tests with devtools #20832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds two
yarn
/npm run
aliases;yarn jest:inspect
will run jest throughnode --inspect
yarn jest:inspect-brk
will run jest throughnode --inspect-brk
The difference is that one (
--inspect-brk
) will wait for the devtools to connect and pause at the start. This one requires you to explicitly press the start button before the code starts running (once hooked up). The other one (--inspect
) will start running immediately after connecting to devtools.(For anyone looking at this; The way you use this is to go to chrome/chromium and open the pseudo-url
about:inspect
. In there click the "open dedicated window for node" link (see screencap). Once that window is open,node --inspect
andnode --inspect-brk
will automatically start debug sessions in that devtools popup. To debug a Gatsby test you would runyarn jest:inspect some/feat.js -t "test case"
. )